From: Dmitry Fomichev <Dmitry.Fomichev@wdc.com>
To: "fio@vger.kernel.org" <fio@vger.kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: Damien Le Moal <Damien.LeMoal@wdc.com>,
Niklas Cassel <Niklas.Cassel@wdc.com>
Subject: Re: [PATCH v2 4/5] HOWTO/man: Describe trim support by zone reset for zoned devices
Date: Thu, 5 Aug 2021 19:04:03 +0000 [thread overview]
Message-ID: <5b52178493ed1eea4966aa9cedebfd01cdbe332b.camel@wdc.com> (raw)
In-Reply-To: <20210805032835.1119908-5-shinichiro.kawasaki@wdc.com>
On Thu, 2021-08-05 at 12:28 +0900, Shin'ichiro Kawasaki wrote:
> Previous commits added trim support for zoned devices. Update HOWTO and
> man page to describe it. Also add missing description about libzbc I/O
> engine to HOWTO.
>
> Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
> ---
> HOWTO | 9 +++++++++
> fio.1 | 4 +++-
> 2 files changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/HOWTO b/HOWTO
> index d4e620de..b5d71475 100644
> --- a/HOWTO
> +++ b/HOWTO
> @@ -992,6 +992,9 @@ Target file/device
> single zone. The :option:`zoneskip`
> parameter
> is ignored. :option:`zonerange` and
> :option:`zonesize` must be identical.
> + Trim is handled using a zone reset
> operation.
> + Trim only considers non-empty
> sequential write
> + required and sequential write preferred
> zones.
>
> .. option:: zonerange=int
>
> @@ -1965,6 +1968,12 @@ I/O engine
> character devices. This engine supports trim
> operations.
> The sg engine includes engine specific options.
>
> + **libzbc**
> + Synchronous I/O engine for SMR hard-disks using
> the libzbc
> + library. The target can be either an sg
> character device or
> + a block device file. This engine supports the
> zonemode=zbd zone
> + operations and read/write/trim I/Os.
> +
May I suggest an even shorter description here?
Read, write, trim and ZBC/ZAC operations to a zoned block device using
libzbc library. The target can be either an SG character device or
a block device file.
> **null**
> Doesn't transfer any data, just pretends to.
> This is mainly used to
> exercise fio itself and for debugging/testing
> purposes.
> diff --git a/fio.1 b/fio.1
> index 9c12ad13..c0e83fef 100644
> --- a/fio.1
> +++ b/fio.1
> @@ -766,6 +766,8 @@ starts. The \fBzonecapacity\fR parameter is
> ignored.
> Zoned block device mode. I/O happens sequentially in each zone, even
> if random
> I/O has been selected. Random I/O happens across all zones instead of
> being
> restricted to a single zone.
> +Trim is handled using a zone reset operation. Trim only considers non-
> empty
> +sequential write required and sequential write preferred zones.
> .RE
> .RE
> .TP
> @@ -1764,7 +1766,7 @@ sg engine includes engine specific options.
> Synchronous I/O engine for SMR hard-disks using the \fBlibzbc\fR
> library. The target can be either an sg character device or
> a block device file. This engine supports the zonemode=zbd zone
> -operations.
> +operations and read/write/trim I/Os.
> .TP
> .B null
> Doesn't transfer any data, just pretends to. This is mainly used to
next prev parent reply other threads:[~2021-08-05 19:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 3:28 [PATCH v2 0/5] zbd: Support zone reset by trim Shin'ichiro Kawasaki
2021-08-05 3:28 ` [PATCH v2 1/5] zbd: Add min_bytes argument to zbd_find_zone() Shin'ichiro Kawasaki
2021-08-05 3:28 ` [PATCH v2 2/5] zbd: Support zone reset by trim Shin'ichiro Kawasaki
2021-08-05 3:28 ` [PATCH v2 3/5] engines/libzbc: Enable trim for libzbc I/O engine Shin'ichiro Kawasaki
2021-08-05 3:28 ` [PATCH v2 4/5] HOWTO/man: Describe trim support by zone reset for zoned devices Shin'ichiro Kawasaki
2021-08-05 19:04 ` Dmitry Fomichev [this message]
2021-08-05 3:28 ` [PATCH v2 5/5] t/zbd: Add test #58 to test zone reset by trim workload Shin'ichiro Kawasaki
2021-08-05 19:04 ` [PATCH v2 0/5] zbd: Support zone reset by trim Dmitry Fomichev
2021-08-06 1:06 ` Shinichiro 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=5b52178493ed1eea4966aa9cedebfd01cdbe332b.camel@wdc.com \
--to=dmitry.fomichev@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=Niklas.Cassel@wdc.com \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.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 NNTP newsgroup(s).