On Sat, 10 Aug 2024 10:08:29 +0800 Yu Kuai <yukuai1@xxxxxxxxxxxxxxx> wrote: > From: Yu Kuai <yukuai3@xxxxxxxxxx> > > The structure is empty for now, and will be used in later patches to > merge in bitmap operations, prepare to implement a new lock free > bitmap in the fulture. HI Kuai, typo: future I think that as "later" you meant next patches in this patchset, right? If yes, Please you "next" instead. At this point bringing "lock free implementation in the future" looks like totally unnecessary. It may happen or may not. Eventually, You can mention it in cover letter. What we have now is the most important. This is just a code rework. The main goal of this (as you mentioned in second patch): "So that the implementation won't be exposed, and it'll be possible to invent a new bitmap by replacing bitmap_operations." but please mention that you are not going to implement second mechanism to not confuse reader. You need it to improve code maintainability mainly I think. I would mention something about common "struct _ops" pattern (the special structure to keep related operations together) that it is going to follow now. For me, this one can be easy merged with the patch 2, so we will got struct + usage in one patch. Anyway, LGTM. Thanks, Mariusz
