[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250512132427.GA31781@lst.de>
Date: Mon, 12 May 2025 15:24:27 +0200
From: Christoph Hellwig <hch@....de>
To: Yu Kuai <yukuai1@...weicloud.com>
Cc: Christoph Hellwig <hch@....de>, xni@...hat.com, colyli@...nel.org,
agk@...hat.com, snitzer@...nel.org, mpatocka@...hat.com,
song@...nel.org, linux-kernel@...r.kernel.org,
dm-devel@...ts.linux.dev, linux-raid@...r.kernel.org,
yi.zhang@...wei.com, yangerkun@...wei.com, johnny.chenyi@...wei.com,
"yukuai (C)" <yukuai3@...wei.com>
Subject: Re: [PATCH RFC md-6.16 v3 10/19] md/md-llbitmap: add data
structure definition and comments
On Mon, May 12, 2025 at 04:05:58PM +0800, Yu Kuai wrote:
> I'm not sure, this way is simpiler, however do you prefer add structure
> and comments by following patches gradually?
In general it's easier if code that belongs together is added in
one go. Separate modules in the sense of they don't really
depend on the surroundings separately
>>> + */
>>> +struct llbitmap_barrier {
>>> + char *data;
>>
>> This is really a states array as far as I can tell. Maybe name it
>> more descriptively and throw in a comment.
>
> How about llbitmap_page_ctl ?
I mean the data pointer which really is states. No real comment
on the structure name.
Powered by blists - more mailing lists