public inbox for fio@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent Fu <vincentfu@gmail.com>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	fio@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Cc: Damien Le Moal <dlemoal@kernel.org>,
	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 11:16:10 -0500	[thread overview]
Message-ID: <e6b1b453-d185-4ca8-91f2-302333875999@gmail.com> (raw)
In-Reply-To: <20250122013835.1223725-1-shinichiro.kawasaki@wdc.com>

On 1/21/25 8:38 PM, 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.
> 
> Changes from v1:
> * 1st patch: added Fixes tags
> 
> 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(+)
> 


Applied. Thanks.

Vincent

      parent reply	other threads:[~2025-01-22 16:16 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
2025-01-22 16:16 ` Vincent Fu [this message]

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=e6b1b453-d185-4ca8-91f2-302333875999@gmail.com \
    --to=vincentfu@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=dlemoal@kernel.org \
    --cc=fio@vger.kernel.org \
    --cc=niklas.cassel@wdc.com \
    --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