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 <damien.lemoal@opensource.wdc.com>,
Dmitry Fomichev <Dmitry.Fomichev@wdc.com>,
Niklas Cassel <niklas.cassel@wdc.com>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: [PATCH 0/4] clarify usage of options for zonemode=zbd
Date: Thu, 15 Dec 2022 10:56:02 +0900 [thread overview]
Message-ID: <20221215015606.2767187-1-shinichiro.kawasaki@wdc.com> (raw)
Options for zonemode=zbd have some confusions. Clarify their usage by improving
HOWTO/man descriptions and example scripts. The first patch fixes a minor issue
found during man page update. The second patch improves the descriptions about
max_open_zones and job_max_open_zones. The third and forth patches show how to
use zone_reset_threshold, zone_reset_frequency, trim workload and 'z' postfix of
size option.
Shin'ichiro Kawasaki (4):
man: fix troff warning
HOWTO/man: improve descriptions of max open zones options
example: add a zoned block device write example with GC by zone resets
example: add a zoned block device write example with GC by trim
workload
HOWTO.rst | 27 ++++++++++----
examples/zbd-rand-write-trim-gc.fio | 43 ++++++++++++++++++++++
examples/zbd-rand-write-trim-gc.png | Bin 0 -> 104661 bytes
examples/zbd-rand-write-zone-reset-gc.fio | 27 ++++++++++++++
examples/zbd-rand-write-zone-reset-gc.png | Bin 0 -> 59186 bytes
fio.1 | 25 +++++++++----
6 files changed, 108 insertions(+), 14 deletions(-)
create mode 100644 examples/zbd-rand-write-trim-gc.fio
create mode 100644 examples/zbd-rand-write-trim-gc.png
create mode 100644 examples/zbd-rand-write-zone-reset-gc.fio
create mode 100644 examples/zbd-rand-write-zone-reset-gc.png
--
2.37.1
next reply other threads:[~2022-12-15 1:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 1:56 Shin'ichiro Kawasaki [this message]
2022-12-15 1:56 ` [PATCH 1/4] man: fix troff warning Shin'ichiro Kawasaki
2022-12-15 1:56 ` [PATCH 2/4] HOWTO/man: improve descriptions of max open zones options Shin'ichiro Kawasaki
2022-12-15 5:39 ` Damien Le Moal
2022-12-15 1:56 ` [PATCH 3/4] example: add a zoned block device write example with GC by zone resets Shin'ichiro Kawasaki
2022-12-15 1:56 ` [PATCH 4/4] example: add a zoned block device write example with GC by trim workload Shin'ichiro Kawasaki
2022-12-15 19:42 ` [PATCH 0/4] clarify usage of options for zonemode=zbd Jens Axboe
2022-12-19 17:00 ` 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=20221215015606.2767187-1-shinichiro.kawasaki@wdc.com \
--to=shinichiro.kawasaki@wdc.com \
--cc=Dmitry.Fomichev@wdc.com \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@opensource.wdc.com \
--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 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.