[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f577e147-c692-97b1-3262-2684649b5eae@samsung.com>
Date: Fri, 29 Jul 2022 11:09:14 +0200
From: Pankaj Raghav <p.raghav@...sung.com>
To: Bart Van Assche <bvanassche@....org>,
<damien.lemoal@...nsource.wdc.com>, <hch@....de>,
<axboe@...nel.dk>, <snitzer@...nel.org>,
<Johannes.Thumshirn@....com>
CC: <matias.bjorling@....com>, <gost.dev@...sung.com>,
<linux-kernel@...r.kernel.org>, <hare@...e.de>,
<linux-block@...r.kernel.org>, <pankydev8@...il.com>,
<jaegeuk@...nel.org>, <dm-devel@...hat.com>,
<linux-nvme@...ts.infradead.org>,
Luis Chamberlain <mcgrof@...nel.org>
Subject: Re: [PATCH v8 02/11] block: allow blk-zoned devices to have
non-power-of-2 zone size
On 2022-07-28 15:29, Bart Van Assche wrote:
>> But I am fine with going back to bdev_is_zone_start if you and Damien
>> feel strongly otherwise.
> The "zone start LBA" terminology occurs in ZBC-1, ZBC-2 and ZNS but
> "zone aligned" not. I prefer "zone start" because it is clear,
> unambiguous and because it has the same meaning as in the corresponding
> standards documents. I propose to proceed as follows for checking
> whether a number of LBAs is a multiple of the zone length:
> * Either use bdev_is_zone_start() directly.
> * Or introduce a synonym for bdev_is_zone_start() with an appropriate
> name, e.g. bdev_is_zone_len_multiple().
>
Thanks for the clarification Bart. I will go with bdev_is_zone_start()
as it is also a commonly used terminology.
> Thanks,
>
> Bart.
Powered by blists - more mailing lists