From: Bart Van Assche <bvanassche@acm.org>
To: Damien Le Moal <dlemoal@kernel.org>, Ming Lei <ming.lei@redhat.com>
Cc: linux-block@vger.kernel.org, Yi Zhang <yi.zhang@redhat.com>,
John Meneghini <jmeneghi@redhat.com>,
linux-nvme@lists.infradead.org, hch@lst.de,
Keith Busch <kbusch@kernel.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
"linux-scsi @ vger . kernel . org" <linux-scsi@vger.kernel.org>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Pankaj Raghav <p.raghav@samsung.com>
Subject: Re: [Report] blk-zoned/ZNS: non_power_of_2 of zone->len]
Date: Thu, 11 Jan 2024 19:46:36 -0800 [thread overview]
Message-ID: <5eed1649-135d-445c-b725-c6ae2d76b699@acm.org> (raw)
In-Reply-To: <6fe89190-a8ff-47c3-a6c4-7d69296c9883@kernel.org>
On 1/11/24 19:34, Damien Le Moal wrote:
> On 1/12/24 12:29, Ming Lei wrote:
>> Just saw Bart's work on supporting non-power_of_2 zone len:
>>
>> https://lore.kernel.org/linux-block/dc89c70e-4931-baaf-c450-6801c200c1d7@acm.org/
Hmm ... weren't these patches developed by Pankaj Raghav from Samsung?
>> IMO FS support might be another topic, cause FS isn't the only user,
>> also without block layer support, the device isn't usable, not mention FS.
>
> And if the FS requires a power of 2 zone size, that will create fragmentation of
> the zoned device support: some devices will be usable with an FS, others not.
> Not nice at all. That is *not* something that exists today, for any block
> device. I am not very keen on going down such route.
F2FS supports zone sizes that are not a power of two. Recent Android
kernels have support for zone sizes that are not a power of two in the
block layer since UFS vendors requested support for this. We prefer to
have support in the upstream kernel for zone sizes that are not a power
of two because having to carry out-of-tree patches is painful.
Thanks,
Bart.
next prev parent reply other threads:[~2024-01-12 3:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 1:13 [Report] blk-zoned/ZNS: non_power_of_2 of zone->len] Ming Lei
2024-01-12 3:05 ` Damien Le Moal
2024-01-12 3:29 ` Ming Lei
2024-01-12 3:34 ` Damien Le Moal
2024-01-12 3:46 ` Bart Van Assche [this message]
2024-01-12 15:40 ` Pankaj Raghav (Samsung)
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=5eed1649-135d-445c-b725-c6ae2d76b699@acm.org \
--to=bvanassche@acm.org \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=jaegeuk@kernel.org \
--cc=jmeneghi@redhat.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=p.raghav@samsung.com \
--cc=yi.zhang@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