From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: fio@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Cc: Damien Le Moal <Damien.LeMoal@wdc.com>,
Dmitry Fomichev <Dmitry.Fomichev@wdc.com>,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: [PATCH v3 0/7] Improve open zones accounting
Date: Tue, 1 Sep 2020 17:19:59 +0900 [thread overview]
Message-ID: <20200901082006.1476720-1-shinichiro.kawasaki@wdc.com> (raw)
The max_open_zones and job_max_open_zones option control number of write target
open zones within the specified limit. Currently, this write target zone
accounting is not accurate enough. Even with these options set, the limits can
exceed during write workloads.
This patch series improves accuracy of the open zones accounting. The first
patch moves the moment to decrement number of currently open zones from write
command submit to write command completion. This avoids zone writes beyond the
limit caused by concurrent write commands at queue depths approaching the max
limits. The second and third patches fix the open zone status initialization
issue. Other following patches improve t/zbd scripts to take maximum write
target zone limit and allow to test devices with the limit.
Changes from v2:
* Improved code comment per review on the list
Changes from v1:
* Improved open zones list initialization to reset zones beyond max open zones
* Added the 2nd patch which is required for the open zones list initialization
* Reflected various comments on the list
Shin'ichiro Kawasaki (7):
zbd: Decrement open zones count at write command completion
oslib/linux-blkzoned: Allow reset zone before file set up
zbd: Initialize open zones list referring zone status at fio start
t/zbd: Improve usage message of test-zbd-support script
t/zbd: Add -o option to t/zbd/test-zoned-support
t/zbd: Reset all zones before test when max open zones is specified
t/zbd: Remove unnecessary option for zbc_reset_zone
io_u.c | 4 +-
io_u.h | 5 +-
ioengines.c | 4 +-
oslib/linux-blkzoned.c | 18 +++++-
t/zbd/functions | 2 +-
t/zbd/test-zbd-support | 122 +++++++++++++++++++++++++++++++++------
zbd.c | 127 +++++++++++++++++++++++++++++++++--------
zbd.h | 9 +--
8 files changed, 236 insertions(+), 55 deletions(-)
--
2.26.2
next reply other threads:[~2020-09-01 8:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 8:19 Shin'ichiro Kawasaki [this message]
2020-09-01 8:20 ` [PATCH v3 1/7] zbd: Decrement open zones count at write command completion Shin'ichiro Kawasaki
2020-09-01 8:20 ` [PATCH v3 2/7] oslib/linux-blkzoned: Allow reset zone before file set up Shin'ichiro Kawasaki
2020-09-01 8:20 ` [PATCH v3 3/7] zbd: Initialize open zones list referring zone status at fio start Shin'ichiro Kawasaki
2020-09-01 8:20 ` [PATCH v3 4/7] t/zbd: Improve usage message of test-zbd-support script Shin'ichiro Kawasaki
2020-09-01 8:20 ` [PATCH v3 5/7] t/zbd: Add -o option to t/zbd/test-zoned-support Shin'ichiro Kawasaki
2020-09-01 8:20 ` [PATCH v3 6/7] t/zbd: Reset all zones before test when max open zones is specified Shin'ichiro Kawasaki
2020-09-01 8:20 ` [PATCH v3 7/7] t/zbd: Remove unnecessary option for zbc_reset_zone Shin'ichiro Kawasaki
2020-09-01 14:38 ` [PATCH v3 0/7] Improve open zones accounting Jens Axboe
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=20200901082006.1476720-1-shinichiro.kawasaki@wdc.com \
--to=shinichiro.kawasaki@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=Dmitry.Fomichev@wdc.com \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
/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.