From: Niklas Cassel <Niklas.Cassel@wdc.com>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>, Vincent Fu <vincentfu@gmail.com>,
Damien Le Moal <dlemoal@kernel.org>
Subject: Re: [PATCH 0/2] zbd: fix open zone status check for non-write jobs
Date: Tue, 21 Jan 2025 09:14:06 +0000 [thread overview]
Message-ID: <Z49lXkn6UvcohDum@ryzen> (raw)
In-Reply-To: <20250121083913.1216619-1-shinichiro.kawasaki@wdc.com>
Hello Shin'ichiro,
On Tue, Jan 21, 2025 at 05:39:11PM +0900, Shin'ichiro Kawasaki wrote:
> Currently, fio checks if each zone within the IO range is in an open
> condition or not. This check is done even if the job does not perform
> any write operations, and causes confusion among users.
>
> This series addresses the problem. The first patch fixes it, and the
> second patch adds a test case to confirm the fix.
If the first patch fixes something, then perhaps it should have a Fixes tag?
I guess the commit
8ac768899d63 ("zbd: do not reset extra zones in open conditions")
is the proper one to reference here?
Kind regards,
Niklas
>
> Shin'ichiro Kawasaki (2):
> zbd: do not check open zones status and limits when jobs do not write
> t/zbd: add test case to confirm no max_open_zones limit check
>
> t/zbd/test-zbd-support | 29 +++++++++++++++++++++++++++++
> zbd.c | 10 ++++++++++
> 2 files changed, 39 insertions(+)
>
> --
> 2.47.0
>
>
next prev parent reply other threads:[~2025-01-21 9:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 8:39 [PATCH 0/2] zbd: fix open zone status check for non-write jobs Shin'ichiro Kawasaki
2025-01-21 8:39 ` [PATCH 1/2] zbd: do not check open zones status and limits when jobs do not write Shin'ichiro Kawasaki
2025-01-21 9:17 ` Niklas Cassel
2025-01-22 1:11 ` Shinichiro Kawasaki
2025-01-21 8:39 ` [PATCH 2/2] t/zbd: add test case to confirm no max_open_zones limit check Shin'ichiro Kawasaki
2025-01-21 8:49 ` [PATCH 0/2] zbd: fix open zone status check for non-write jobs fiotestbot
2025-01-21 9:14 ` Niklas Cassel [this message]
2025-01-22 1:02 ` Shinichiro Kawasaki
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=Z49lXkn6UvcohDum@ryzen \
--to=niklas.cassel@wdc.com \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=fio@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.com \
--cc=vincentfu@gmail.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