From: Bart Van Assche <bvanassche@acm.org>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Pankaj Raghav <p.raghav@samsung.com>,
hch@lst.de, axboe@kernel.dk, snitzer@kernel.org,
Johannes.Thumshirn@wdc.com
Cc: matias.bjorling@wdc.com, gost.dev@samsung.com,
linux-kernel@vger.kernel.org, hare@suse.de,
linux-block@vger.kernel.org, pankydev8@gmail.com,
jaegeuk@kernel.org, dm-devel@redhat.com,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH v8 00/11] support non power of 2 zoned device
Date: Wed, 27 Jul 2022 19:58:00 -0700 [thread overview]
Message-ID: <024d16ac-d685-0fcf-1ad3-e99946852b03@acm.org> (raw)
In-Reply-To: <f2f29f97-5994-37f9-c922-31158c1c1b9a@opensource.wdc.com>
On 7/27/22 18:52, Damien Le Moal wrote:
> On 7/28/22 08:19, Bart Van Assche wrote:
>> On 7/27/22 09:22, Pankaj Raghav wrote:
>>> This series adds support to npo2 zoned devices in the block and nvme
>>> layer and a new **dm target** is added: dm-po2z-target. This new
>>> target will be initially used for filesystems such as btrfs and
>>> f2fs that does not have native npo2 zone support.
>>
>> Should any SCSI changes be included in this patch series? From sd_zbc.c:
>>
>> if (!is_power_of_2(zone_blocks)) {
>> sd_printk(KERN_ERR, sdkp,
>> "Zone size %llu is not a power of two.\n",
>> zone_blocks);
>> return -EINVAL;
>> }
>
> There are no non-power of 2 SMR drives on the market and no plans to have
> any as far as I know. Users want power of 2 zone size. So I think it is
> better to leave sd_zbc & scsi_debug as is for now.
Zoned UFS devices will support ZBC and may have a zone size that is not
a power of two.
Thanks,
Bart.
next prev parent reply other threads:[~2022-07-28 2:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220727162246eucas1p1a758799f13d36ba99d30bf92cc5e2754@eucas1p1.samsung.com>
2022-07-27 16:22 ` [PATCH v8 00/11] support non power of 2 zoned device Pankaj Raghav
2022-07-27 16:22 ` [PATCH v8 01/11] block: make bdev_nr_zones and disk_zone_no generic for npo2 zsze Pankaj Raghav
2022-07-28 2:54 ` Damien Le Moal
2022-07-27 16:22 ` [PATCH v8 02/11] block: allow blk-zoned devices to have non-power-of-2 zone size Pankaj Raghav
2022-07-27 23:16 ` Bart Van Assche
2022-07-28 12:11 ` Pankaj Raghav
2022-07-28 13:29 ` Bart Van Assche
2022-07-29 9:09 ` Pankaj Raghav
2022-07-28 3:07 ` Damien Le Moal
2022-07-28 12:24 ` Pankaj Raghav
2022-07-27 16:22 ` [PATCH v8 03/11] nvme: zns: Allow ZNS drives that have non-power_of_2 " Pankaj Raghav
2022-07-27 16:22 ` [PATCH v8 04/11] nvmet: Allow ZNS target to support non-power_of_2 zone sizes Pankaj Raghav
2022-07-28 3:09 ` Damien Le Moal
2022-07-29 7:45 ` Pankaj Raghav
2022-07-27 16:22 ` [PATCH v8 05/11] null_blk: allow non power of 2 zoned devices Pankaj Raghav
2022-07-27 21:59 ` Chaitanya Kulkarni
2022-07-29 7:51 ` Pankaj Raghav
2022-07-28 3:14 ` Damien Le Moal
2022-07-27 16:22 ` [PATCH v8 06/11] zonefs: " Pankaj Raghav
2022-07-28 3:16 ` Damien Le Moal
2022-07-27 16:22 ` [PATCH v8 07/11] dm-zoned: ensure only power of 2 zone sizes are allowed Pankaj Raghav
2022-07-28 3:18 ` Damien Le Moal
2022-07-28 12:15 ` David Sterba
2022-07-29 8:00 ` Pankaj Raghav
2022-07-27 16:22 ` [PATCH v8 08/11] dm-zone: use generic helpers to calculate offset from zone start Pankaj Raghav
2022-07-28 3:20 ` Damien Le Moal
2022-07-27 16:22 ` [PATCH v8 09/11] dm-table: allow non po2 zoned devices Pankaj Raghav
2022-07-28 3:22 ` Damien Le Moal
2022-07-27 16:22 ` [PATCH v8 10/11] dm: call dm_zone_endio after the target endio callback for " Pankaj Raghav
2022-07-28 3:25 ` Damien Le Moal
2022-07-29 8:48 ` Pankaj Raghav
2022-07-27 16:22 ` [PATCH v8 11/11] dm: add power-of-2 zoned target for non-power-of-2 " Pankaj Raghav
2022-07-28 4:33 ` Damien Le Moal
2022-08-01 8:35 ` Pankaj Raghav
2022-07-27 23:19 ` [PATCH v8 00/11] support non power of 2 zoned device Bart Van Assche
2022-07-28 1:52 ` Damien Le Moal
2022-07-28 2:58 ` Bart Van Assche [this message]
2022-07-28 3:28 ` Damien Le Moal
2022-07-28 11:57 ` Pankaj Raghav
2022-07-28 13:30 ` Bart Van Assche
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=024d16ac-d685-0fcf-1ad3-e99946852b03@acm.org \
--to=bvanassche@acm.org \
--cc=Johannes.Thumshirn@wdc.com \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@opensource.wdc.com \
--cc=dm-devel@redhat.com \
--cc=gost.dev@samsung.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jaegeuk@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=matias.bjorling@wdc.com \
--cc=p.raghav@samsung.com \
--cc=pankydev8@gmail.com \
--cc=snitzer@kernel.org \
/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