From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: fio@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Vincent Fu <vincentfu@gmail.com>
Cc: Damien Le Moal <dlemoal@kernel.org>,
Dmitry Fomichev <Dmitry.Fomichev@wdc.com>,
Niklas Cassel <niklas.cassel@wdc.com>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: [PATCH 0/7] zbd: clean up code and fix bugs for open zones accounting
Date: Wed, 7 Jun 2023 17:32:23 +0900 [thread overview]
Message-ID: <20230607083230.1178573-1-shinichiro.kawasaki@wdc.com> (raw)
Fio with zonemode=zbd does accounting of 'open zones'. However, the meaning of
'open zone' is confusing because its definition is similar but different
between fio and zoned block devices. The first patch in this series avoids the
confusion by renaming the word 'open zone' to 'write zone'.
Also, recently three bugs were found related to the open zones accounting.
Following three patches fix the bugs. The last three patches improve test cases
corresponding to the fixes.
Shin'ichiro Kawasaki (7):
zbd: rename 'open zones' to 'write zones'
zbd: do not reset extra zones in open conditions
zbd: fix write zone accounting of almost full zones
zbd: fix write zone accounting of trim workload
t/zbd: reset zones before tests with max_open_zones option
t/zbd: test write zone accounting of almost full zones
t/zbd: test write zone accounting of trim workload
engines/io_uring.c | 2 +-
fio.h | 2 +-
io_u.c | 2 +-
io_u.h | 2 +-
options.c | 4 +-
t/zbd/test-zbd-support | 64 ++++++++-
zbd.c | 293 ++++++++++++++++++++++++-----------------
zbd.h | 25 ++--
zbd_types.h | 2 +-
9 files changed, 249 insertions(+), 147 deletions(-)
--
2.40.1
next reply other threads:[~2023-06-07 8:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 8:32 Shin'ichiro Kawasaki [this message]
2023-06-07 8:32 ` [PATCH 1/7] zbd: rename 'open zones' to 'write zones' Shin'ichiro Kawasaki
2023-06-07 13:15 ` Niklas Cassel
2023-06-07 8:32 ` [PATCH 2/7] zbd: do not reset extra zones in open conditions Shin'ichiro Kawasaki
2023-06-07 13:15 ` Niklas Cassel
2023-06-07 8:32 ` [PATCH 3/7] zbd: fix write zone accounting of almost full zones Shin'ichiro Kawasaki
2023-06-07 13:15 ` Niklas Cassel
2023-06-07 8:32 ` [PATCH 4/7] zbd: fix write zone accounting of trim workload Shin'ichiro Kawasaki
2023-06-07 13:15 ` Niklas Cassel
2023-06-08 5:48 ` Shinichiro Kawasaki
2023-06-08 8:10 ` Niklas Cassel
2023-06-07 15:32 ` Jens Axboe
2023-06-08 5:49 ` Shinichiro Kawasaki
2023-06-07 8:32 ` [PATCH 5/7] t/zbd: reset zones before tests with max_open_zones option Shin'ichiro Kawasaki
2023-06-07 8:32 ` [PATCH 6/7] t/zbd: test write zone accounting of almost full zones Shin'ichiro Kawasaki
2023-06-07 8:32 ` [PATCH 7/7] t/zbd: test write zone accounting of trim workload Shin'ichiro Kawasaki
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=20230607083230.1178573-1-shinichiro.kawasaki@wdc.com \
--to=shinichiro.kawasaki@wdc.com \
--cc=Dmitry.Fomichev@wdc.com \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=fio@vger.kernel.org \
--cc=niklas.cassel@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).