public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Pankaj Raghav <p.raghav@samsung.com>,
	Bart Van Assche <bvanassche@acm.org>,
	hch@lst.de, snitzer@redhat.com, axboe@kernel.dk
Cc: pankydev8@gmail.com, gost.dev@samsung.com,
	jiangbo.365@bytedance.com, linux-nvme@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
	dm-devel@redhat.com, Luis Chamberlain <mcgrof@kernel.org>,
	jonathan.derrick@linux.dev, Johannes.Thumshirn@wdc.com,
	dsterba@suse.com, jaegeuk@kernel.org
Subject: Re: [dm-devel] [PATCH v7 02/13] block: allow blk-zoned devices to have non-power-of-2 zone size
Date: Fri, 17 Jun 2022 08:30:46 +0900	[thread overview]
Message-ID: <ab75c1ca-986f-c3af-6c8c-c2c5b7e40bbd@opensource.wdc.com> (raw)
In-Reply-To: <e04db101-5628-2a1d-6b5c-997090484d7d@samsung.com>

On 6/16/22 19:09, Pankaj Raghav wrote:
> On 2022-06-15 22:28, Bart Van Assche wrote:
> isk_name, zone->len);
>>> +        if (zone->len == 0) {
>>> +            pr_warn("%s: Invalid zone size", disk->disk_name);
>>> +            return -ENODEV;
>>> +        }
>>> +
>>> +        /*
>>> +         * Don't allow zoned device with non power_of_2 zone size with
>>> +         * zone capacity less than zone size.
>>> +         */
>>
> 
>> Please change "power_of_2" into "power-of-2".
>>
> Ok.
>>> +        if (!is_power_of_2(zone->len) && zone->capacity < zone->len) {
>>> +            pr_warn("%s: Invalid zone capacity for non power of 2
>>> zone size",
>>> +                disk->disk_name);
>>>               return -ENODEV;
>>>           }
>>
>> The above check seems wrong to me. I don't see why devices that report a
>> capacity that is less than the zone size should be rejected.
>>
> This was brought up by Damien during previous reviews. The argument was
> that the reason to allow non power-of-2 zoned device is to remove the
> gaps between zone size and zone capacity. Allowing a npo2 zone size with
> a different capacity, even though it is technically possible, it does
> not make any practical sense. That is why this check was introduced.
> Does that answer your question?

Add a comment explaining this restriction, clearly mentioning that it is a
Linux restrictions and not mandated by the specifications.

>>> +        /*
>>> +         * Division is used to calculate nr_zones for both power_of_2
>>> +         * and non power_of_2 zone sizes as it is not in the hot path.
>>> +         */
>>
>> Shouldn't the above comment be moved to the patch description? I'm not
>> sure whether having such a comment in the source code is valuable.
>>
> Yeah, I will remove it. Maybe it is very obvious at this point.
>>> +static inline sector_t blk_queue_offset_from_zone_start(struct
>>> request_queue *q,
>>> +                            sector_t sec)
>>> +{
>>> +    sector_t zone_sectors = blk_queue_zone_sectors(q);
>>> +    u64 remainder = 0;
>>> +
>>> +    if (!blk_queue_is_zoned(q))
>>> +        return false;
>>
>> "return false" should only occur in functions returning a boolean. This
>> function returns type sector_t.
>>
> Good catch. It was a copy paste mistake. Fixed it.
>> Thanks,
>>
>> Bart.
> 
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://listman.redhat.com/mailman/listinfo/dm-devel


-- 
Damien Le Moal
Western Digital Research


  parent reply	other threads:[~2022-06-16 23:31 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20220615101924eucas1p27fbce623c0e1b3097169bf23dd6266d8@eucas1p2.samsung.com>
2022-06-15 10:19 ` [PATCH v7 00/13] support non power of 2 zoned device Pankaj Raghav
2022-06-15 10:19   ` [PATCH v7 01/13] block: make blkdev_nr_zones and blk_queue_zone_no generic for npo2 zsze Pankaj Raghav
2022-06-15 20:18     ` [dm-devel] " Bart Van Assche
2022-06-15 10:19   ` [PATCH v7 02/13] block: allow blk-zoned devices to have non-power-of-2 zone size Pankaj Raghav
2022-06-15 20:28     ` [dm-devel] " Bart Van Assche
2022-06-16 10:09       ` Pankaj Raghav
2022-06-16 16:04         ` Luis Chamberlain
2022-06-16 23:30         ` Damien Le Moal [this message]
2022-06-15 10:19   ` [PATCH v7 03/13] nvme: zns: Allow ZNS drives that have non-power_of_2 " Pankaj Raghav
2022-06-15 10:19   ` [PATCH v7 04/13] nvmet: Allow ZNS target to support non-power_of_2 zone sizes Pankaj Raghav
2022-06-15 10:19   ` [PATCH v7 05/13] null_blk: allow non power of 2 zoned devices Pankaj Raghav
2022-06-15 10:19   ` [PATCH v7 06/13] null_blk: use zone_size_sects_shift for " Pankaj Raghav
2022-06-15 11:56     ` Damien Le Moal
2022-06-15 10:19   ` [PATCH v7 07/13] zonefs: allow non " Pankaj Raghav
2022-06-15 10:19   ` [PATCH v7 08/13] dm-zoned: ensure only power of 2 zone sizes are allowed Pankaj Raghav
2022-06-15 10:19   ` [PATCH v7 09/13] dm-zone: use generic helpers to calculate offset from zone start Pankaj Raghav
2022-06-15 10:19   ` [PATCH v7 10/13] dm-table: use bdev_is_zone_start helper in device_area_is_invalid() Pankaj Raghav
2022-06-15 11:53     ` Damien Le Moal
2022-06-16  9:55       ` Pankaj Raghav
2022-06-16 23:29         ` Damien Le Moal
2022-06-15 10:19   ` [PATCH v7 11/13] dm-table: allow non po2 zoned devices Pankaj Raghav
2022-06-15 10:19   ` [PATCH v7 12/13] dm: call dm_zone_endio after the target endio callback for " Pankaj Raghav
2022-06-15 11:01     ` [dm-devel] " Damien Le Moal
2022-06-16 12:24       ` Pankaj Raghav
2022-06-16 23:33         ` Damien Le Moal
2022-06-15 10:19   ` [PATCH v7 13/13] dm: add non power of 2 zoned target Pankaj Raghav
2022-06-15 11:49     ` Damien Le Moal
2022-06-16 16:12       ` Pankaj Raghav
2022-06-16 23:49         ` Damien Le Moal
2022-06-17  5:45           ` Pankaj Raghav
2022-06-17  6:12             ` Damien Le Moal
2022-06-17  6:40               ` Pankaj Raghav
2022-06-17  6:56                 ` Damien Le Moal
2022-06-17  8:03                   ` Pankaj Raghav
2022-06-15 14:19     ` kernel test robot
2022-06-15 19:54     ` Randy Dunlap
2022-06-16 10:28       ` Pankaj Raghav

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ab75c1ca-986f-c3af-6c8c-c2c5b7e40bbd@opensource.wdc.com \
    --to=damien.lemoal@opensource.wdc.com \
    --cc=Johannes.Thumshirn@wdc.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=dm-devel@redhat.com \
    --cc=dsterba@suse.com \
    --cc=gost.dev@samsung.com \
    --cc=hch@lst.de \
    --cc=jaegeuk@kernel.org \
    --cc=jiangbo.365@bytedance.com \
    --cc=jonathan.derrick@linux.dev \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=mcgrof@kernel.org \
    --cc=p.raghav@samsung.com \
    --cc=pankydev8@gmail.com \
    --cc=snitzer@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox