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 00/13] zbd: improve max_active_zones limit handling
Date: Fri, 7 Jul 2023 12:14:52 +0900 [thread overview]
Message-ID: <20230707031505.3468915-1-shinichiro.kawasaki@wdc.com> (raw)
Current fio implementation for zonemode=zbd has two problems for zoned
block devices with max_active_zones. The first problem is max_active_zones
limit error. When some of write target zones are in closed condition at fio
start, writes to other zones causes the max_active_zones limit error. The
second problem is a confusing error message. When number of active zones goes
beyond the max_active_zones limit, fio prints unrelated error message and
confuses users [1].
This series addresses the two problems. The first patch is a preparation to get
the max_active_zones value from devices. The next two patches fix the two
problems. The forth patch modifies man document of max_open_zones option to
match with the fixes. Other nine patches improve test scripts for the fixes. Add
test cases and test conditions to confirm the fixes. Also fix test script bugs
found during this work.
[1] https://lore.kernel.org/fio/ZHShQdVGkyRfd6v0@x1-carbon/T/#m4ec7ff1575981e92517c0ea7f699e7df9aba087c
Dmitry Fomichev (2):
t/zbd: fix null_blk configuration in run-tests-against-nullb
t/zbd: add max_active configs to run-tests-against-nullb
Shin'ichiro Kawasaki (11):
zbd: refer max_active_zones sysfs attribute
zbd: write to closed zones on the devices with max_active_zones limit
zbd: print max_active_zones limit error message
docs: modify max_open_zones option description
t/zbd: add close_zone helper function
t/zbd: add max_active_zone variable
t/zbd: add test case to check zones in closed condition
t/zbd: add test case to check max_active_zones limit error message
t/zbd: get max_open_zones from sysfs
t/zbd: fix fio failure check and SG node failure in test case 31
t/zbd: add missing prep_write for test cases with write workloads
HOWTO.rst | 44 +++++---
fio.1 | 36 ++++--
io_u.c | 2 +
oslib/blkzoned.h | 9 ++
oslib/linux-blkzoned.c | 23 ++++
t/zbd/functions | 33 +++++-
t/zbd/run-tests-against-nullb | 203 ++++++++++++++++++++++++++++++++--
t/zbd/test-zbd-support | 91 ++++++++++++++-
zbd.c | 26 ++++-
zbd.h | 5 +
10 files changed, 433 insertions(+), 39 deletions(-)
--
2.40.1
next reply other threads:[~2023-07-07 3:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 3:14 Shin'ichiro Kawasaki [this message]
2023-07-07 3:14 ` [PATCH 01/13] zbd: refer max_active_zones sysfs attribute Shin'ichiro Kawasaki
2023-07-18 13:55 ` Niklas Cassel
2023-07-19 3:10 ` Shinichiro Kawasaki
2023-07-07 3:14 ` [PATCH 02/13] zbd: write to closed zones on the devices with max_active_zones limit Shin'ichiro Kawasaki
2023-07-18 13:55 ` Niklas Cassel
2023-07-07 3:14 ` [PATCH 03/13] zbd: print max_active_zones limit error message Shin'ichiro Kawasaki
2023-07-18 13:55 ` Niklas Cassel
2023-07-19 3:13 ` Shinichiro Kawasaki
2023-07-07 3:14 ` [PATCH 04/13] docs: modify max_open_zones option description Shin'ichiro Kawasaki
2023-07-18 13:56 ` Niklas Cassel
2023-07-19 3:15 ` Shinichiro Kawasaki
2023-07-07 3:14 ` [PATCH 05/13] t/zbd: add close_zone helper function Shin'ichiro Kawasaki
2023-07-07 3:14 ` [PATCH 06/13] t/zbd: add max_active_zone variable Shin'ichiro Kawasaki
2023-07-07 3:14 ` [PATCH 07/13] t/zbd: add test case to check zones in closed condition Shin'ichiro Kawasaki
2023-07-07 3:15 ` [PATCH 08/13] t/zbd: add test case to check max_active_zones limit error message Shin'ichiro Kawasaki
2023-07-07 3:15 ` [PATCH 09/13] t/zbd: get max_open_zones from sysfs Shin'ichiro Kawasaki
2023-07-07 3:15 ` [PATCH 10/13] t/zbd: fix fio failure check and SG node failure in test case 31 Shin'ichiro Kawasaki
2023-07-07 3:15 ` [PATCH 11/13] t/zbd: add missing prep_write for test cases with write workloads Shin'ichiro Kawasaki
2023-07-07 3:15 ` [PATCH 12/13] t/zbd: fix null_blk configuration in run-tests-against-nullb Shin'ichiro Kawasaki
2023-07-07 3:15 ` [PATCH 13/13] t/zbd: add max_active configs to run-tests-against-nullb 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=20230707031505.3468915-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).