From: Damien Le Moal <dlemoal@kernel.org>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
fio@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Vincent Fu <vincentfu@gmail.com>
Cc: Niklas Cassel <niklas.cassel@wdc.com>
Subject: Re: [PATCH v2 0/2] zbd: fix open zone status check for non-write jobs
Date: Wed, 22 Jan 2025 14:59:24 +0900 [thread overview]
Message-ID: <71f6098c-a309-45fb-9af6-0d6afdeb63ab@kernel.org> (raw)
In-Reply-To: <20250122013835.1223725-1-shinichiro.kawasaki@wdc.com>
On 1/22/25 10:38 AM, 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.
Looks good to me. For the series:
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2025-01-22 5:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 1:38 [PATCH v2 0/2] zbd: fix open zone status check for non-write jobs Shin'ichiro Kawasaki
2025-01-22 1:38 ` [PATCH v2 1/2] zbd: do not check open zones status and limits when jobs do not write Shin'ichiro Kawasaki
2025-01-22 8:45 ` Niklas Cassel
2025-01-22 1:38 ` [PATCH v2 2/2] t/zbd: add test case to confirm no max_open_zones limit check Shin'ichiro Kawasaki
2025-01-22 2:59 ` [PATCH v2 0/2] zbd: fix open zone status check for non-write jobs fiotestbot
2025-01-22 5:59 ` Damien Le Moal [this message]
2025-01-22 16:16 ` Vincent Fu
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=71f6098c-a309-45fb-9af6-0d6afdeb63ab@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=niklas.cassel@wdc.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.