From: Sean Anderson <seanga2@gmail.com>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
"hch@infradead.org" <hch@infradead.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH blktests] zbd/005: Limit block size to zone length
Date: Thu, 24 Apr 2025 09:56:11 -0400 [thread overview]
Message-ID: <d683d1fe-7817-f692-addc-93d2fdab39db@gmail.com> (raw)
In-Reply-To: <jzrhzy3qdj7tt2tlmoayo7pi367etl3furcbk3yvuh4zru2q7q@ikekotau7jvl>
On 4/24/25 07:30, Shinichiro Kawasaki wrote:
> On Apr 24, 2025 / 01:09, Christoph Hellwig wrote:
>> On Wed, Apr 23, 2025 at 12:49:57PM -0400, Sean Anderson wrote:
>>> The block size must be smaller than the zone length, otherwise fio will
>>> fail immediately.
>>
>> In theory yes. In practice such a zone size makes zero sense, and will
>> not work with any zoned file systems or other users.
>>
>> So instead we should just warn about a silly zone size here instead
>> of trying to handle it.
>
> As a similar idea, how about to skip the test case if the test target device's
> zone size is too small?
Why would I want that? The test passes with an appropriate block size.
--Sean
next prev parent reply other threads:[~2025-04-24 13:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 16:49 [PATCH blktests] zbd/005: Limit block size to zone length Sean Anderson
2025-04-24 8:09 ` Christoph Hellwig
2025-04-24 11:30 ` Shinichiro Kawasaki
2025-04-24 13:56 ` Sean Anderson [this message]
2025-04-24 14:06 ` hch
2025-04-24 14:20 ` Sean Anderson
2025-04-24 14:23 ` hch
2025-04-25 4:04 ` Sean Anderson
2025-04-25 13:47 ` hch
2025-04-26 5:23 ` Sean Anderson
2025-04-27 3:23 ` Keith Busch
2025-04-25 2:37 ` Damien Le Moal
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=d683d1fe-7817-f692-addc-93d2fdab39db@gmail.com \
--to=seanga2@gmail.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.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