From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Vincent Fu <vincentfu@gmail.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>, Damien Le Moal <dlemoal@kernel.org>
Subject: Re: [PATCH 02/12] zbd: set norandommap=1 when zonemode=zbd is specified
Date: Mon, 9 Feb 2026 23:57:20 +0000 [thread overview]
Message-ID: <aYp0ONUf0UpZnX7y@shinmob> (raw)
In-Reply-To: <CAOp=CXmUB1cf6AgMPqLAVXaKCLxy+B56918MzTGUDtGR1QXTbw@mail.gmail.com>
On Jan 30, 2026 / 15:01, Vincent Fu wrote:
> On Tue, Jan 27, 2026 at 12:05 AM Shinichiro Kawasaki
> <shinichiro.kawasaki@wdc.com> wrote:
> >
> > Vincent, thanks for the comments.
> >
> > On Jan 26, 2026 / 20:39, Vincent Fu wrote:
> [...]
> > >
> > > Perhaps you could instead emit a warning when a random job is run with
> > > a random map and then condition the relevant changes in later patches
> > > on the absence of a random map.
> >
> > Actually, I thought about other options as follows to seek for a better
> > solution:
> >
> > 1) Leave the current remainder handling with zone finish operation, and add the
> > new handling with simple writes. Choose one of the two handlings by a new
> > option, and ensure norandommap=1 only for the handling with simple writes.
> > -> This can keep the current behavior with norandommap=1 workloads, but it
> > comes with the zone finish operation that shows bad performance. I
> > thought this leaves complexity for users and in the code.
>
> The above is my preferred solution. It preserves backward
> compatibility albeit at the cost of additional complexity.
>
> We do have many other situations where some technical knowledge and
> complexity is required to maximize performance.
Okay, thank you for the comment. I will prepare v2 series based on this option.
next prev parent reply other threads:[~2026-02-09 23:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 2:35 [PATCH 00/12] zbd: fix problems of random write with unaligned block size Shin'ichiro Kawasaki
2026-01-09 2:35 ` [PATCH 01/12] zbd: fix zone selection of random writes Shin'ichiro Kawasaki
2026-01-09 2:35 ` [PATCH 02/12] zbd: set norandommap=1 when zonemode=zbd is specified Shin'ichiro Kawasaki
2026-01-27 1:39 ` Vincent Fu
2026-01-27 5:05 ` Shinichiro Kawasaki
2026-01-30 20:01 ` Vincent Fu
2026-02-09 23:57 ` Shinichiro Kawasaki [this message]
2026-01-09 2:35 ` [PATCH 03/12] zbd: write zone remainders smaller than minimum block size Shin'ichiro Kawasaki
2026-01-09 2:35 ` [PATCH 04/12] zbd: fix write zone accounting Shin'ichiro Kawasaki
2026-01-09 2:35 ` [PATCH 05/12] zbd: remove io_u_quiesce() at write target zone switch Shin'ichiro Kawasaki
2026-01-09 2:35 ` [PATCH 06/12] zbd: remove zbd_finish_zone() Shin'ichiro Kawasaki
2026-01-09 2:35 ` [PATCH 07/12] oslib: remove blkzoned_finish_zone() Shin'ichiro Kawasaki
2026-01-09 2:35 ` [PATCH 08/12] ioengine: remove finish_zone() Shin'ichiro Kawasaki
2026-01-09 2:36 ` [PATCH 09/12] doc: explain norandommap restriction and small remainder of zonemode=zbd Shin'ichiro Kawasaki
2026-01-09 2:36 ` [PATCH 10/12] t/zbd: avoid test case 14 failure due to no randam map Shin'ichiro Kawasaki
2026-01-09 2:36 ` [PATCH 11/12] t/zbd: avoid test case 33 failure due to zone end remainder Shin'ichiro Kawasaki
2026-01-09 2:36 ` [PATCH 12/12] t/zbd: avoid test case 71 " Shin'ichiro Kawasaki
2026-01-09 9:19 ` [PATCH 00/12] zbd: fix problems of random write with unaligned block size fiotestbot
2026-01-26 6:50 ` 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=aYp0ONUf0UpZnX7y@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=fio@vger.kernel.org \
--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.