public inbox for fio@vger.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: [PATCH v3 2/8] zbd: fix write zone accounting
Date: Mon, 2 Mar 2026 12:41:49 +0900	[thread overview]
Message-ID: <35cc81d1-ef4e-4b21-88ea-6386075677c3@kernel.org> (raw)
In-Reply-To: <20260302022609.3526823-3-shinichiro.kawasaki@wdc.com>

On 3/2/26 11:26 AM, Shin'ichiro Kawasaki wrote:
> Currently, zbd_convert_to_write_zones() calls io_u_quiesce() when the
> number of write target zones hits one of the limits of write zones. This
> wait by io_u_quiesce() significantly degrade the performance. While I
> tried to remove the io_u_quiesce(), I observed that the test case 58 of
> t/zbd/test-zbd-support failed with null_blk devices that have a
> max_active_zones limit set.
> 
> The failure cause is an incorrect write target zone accounting in
> zbd_convert_to_write_zones(). This function checks the current write
> target zones, and selects one of them as the next write target zone.
> After the zone selection, it locks the zone. However, when the zone is
> locked, another job such as a trim workload or a write workload with the
> zone_reset_threshold option might have already reset the zone and
> removed it from the write target zones array. This unexpected zone
> removal from the array caused an incorrect zone accounting and the test
> case failure.
> 
> To avoid the incorrect zone accounting, call zbd_write_zone_get() after
> the selected zone gets locked. If the zone is removed from the write
> target zones array, the function adds the zone back to the array.
> 
> Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
> ---
>  zbd.c | 13 +++++++++++--
>  1 file changed, 11 insertions(+), 2 deletions(-)
> 
> diff --git a/zbd.c b/zbd.c
> index b71f842c..c511b709 100644
> --- a/zbd.c
> +++ b/zbd.c
> @@ -1693,8 +1693,17 @@ retry:
>  
>  		zone_lock(td, f, z);
>  		if (zbd_zone_remainder(z) >= min_bs) {
> -			need_zone_finish = false;
> -			goto out;
> +			/*
> +			 * The zone might be already removed from
> +			 * zbdi->write_zones[] by other jobs at this moment.
> +			 * Even if the zone has remainder, call
> +			 * zbd_write_zone_get() to ensure that it is in the
> +			 * array.
> +			 */
> +			if (zbd_write_zone_get(td, f, z)) {
> +				need_zone_finish = false;
> +				goto out;
> +			}

Please change this to:

		if (zbd_zone_remainder(z) >= min_bs &&
		    zbd_write_zone_get(td, f, z)) {
			need_zone_finish = false;
			goto out;
		}

And move the comment block above the if. You could also improve the comment to
explain why we look at "zbd_zone_remainder(z) >= min_bs"

With that (and the much better commit message), feel free to add:

Reviewed-by: Damien Le Moal <dlemoal@kernel.org>

>  		}
>  		pthread_mutex_lock(&zbdi->mutex);
>  	}


-- 
Damien Le Moal
Western Digital Research

  reply	other threads:[~2026-03-02  3:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02  2:26 [PATCH v3 0/8] zbd: fix problems of random write with unaligned block size Shin'ichiro Kawasaki
2026-03-02  2:26 ` [PATCH v3 1/8] zbd: fix zone selection of random writes Shin'ichiro Kawasaki
2026-03-02  2:26 ` [PATCH v3 2/8] zbd: fix write zone accounting Shin'ichiro Kawasaki
2026-03-02  3:41   ` Damien Le Moal [this message]
2026-03-02  6:49     ` Shinichiro Kawasaki
2026-03-02  2:26 ` [PATCH v3 3/8] zbd: introduce write_zone_remainder option Shin'ichiro Kawasaki
2026-03-02  4:36   ` Damien Le Moal
2026-03-02  6:51     ` Shinichiro Kawasaki
2026-03-02  2:26 ` [PATCH v3 4/8] doc: explain the option write_zone_remainder Shin'ichiro Kawasaki
2026-03-02  2:26 ` [PATCH v3 5/8] t/zbd: add -m option to enable write_zone_remainder option Shin'ichiro Kawasaki
2026-03-02  2:26 ` [PATCH v3 6/8] t/zbd: avoid test case 14 failure with " Shin'ichiro Kawasaki
2026-03-02  2:26 ` [PATCH v3 7/8] t/zbd: avoid test case 33 " Shin'ichiro Kawasaki
2026-03-02  2:26 ` [PATCH v3 8/8] t/zbd: avoid test case 71 " Shin'ichiro Kawasaki
2026-03-02  5:06 ` [PATCH v3 0/8] zbd: fix problems of random write with unaligned block size fiotestbot

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=35cc81d1-ef4e-4b21-88ea-6386075677c3@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=axboe@kernel.dk \
    --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