From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>, Vincent Fu <vincentfu@gmail.com>
Subject: Re: [PATCH v3 3/8] zbd: introduce write_zone_remainder option
Date: Mon, 2 Mar 2026 06:51:31 +0000 [thread overview]
Message-ID: <aaUzHH-r9eWM9S2Y@shinmob> (raw)
In-Reply-To: <1d1f28e2-cdb0-42a4-ae7a-eaaccac3647b@kernel.org>
On Mar 02, 2026 / 13:36, Damien Le Moal wrote:
[...]
> > enum {
> > - FIO_SERVER_VER = 118,
> > + FIO_SERVER_VER = 119,
>
> Note: this change will conflict with my patches proposing the addition of the
> end_syncfs option.
I see. Since your end_syncfs patches have just applied, I will increment
FIO_SERVER_VER to 120 in my v4 series.
next prev parent reply other threads:[~2026-03-02 6:51 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
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 [this message]
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=aaUzHH-r9eWM9S2Y@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox