From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "email@example.com" <firstname.lastname@example.org>,
Cc: "email@example.com" <firstname.lastname@example.org>,
Damien Le Moal <Damien.LeMoal@wdc.com>
Subject: Re: [PATCH 0/2] null_blk: zone support
Date: Tue, 10 Jul 2018 18:49:17 +0000 [thread overview]
Message-ID: <email@example.com> (raw)
On Tue, 2018-07-10 at 12:45 -0600, Jens Axboe wrote:
> The difference between the job file and the
> workload run can be huge. Consider something really basic:
> which would be 100% random 4k writes. If I run this on a zoned device,
> then that'd turn into 100% sequential writes.
That's not correct. The ZBD code in the github pull request serializes writes
per zone, not globally.
> > What I derived from the fio source code is as follows (please correct me
> > if I got anything wrong):
> > * The purpose of the zonesize, zonerange and zoneskip job options is to
> > limit the I/O range to a single zone with size "zonesize". The I/O
> > pattern for zoned block devices is different: I/O happens in multiple
> > zones simultaneously. The number of zones to which I/O happens is
> > called the number of open zones.
> The only difference is that fio currently only has one zone active. When
> it finishes one, it goes to the next. See my above suggestion on adding
> the notion of open zones, which would extend this to more than 1.
Thanks, I will look into this.
next prev parent reply other threads:[~2018-07-10 18:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 17:38 [PATCH 0/2] null_blk: zone support Matias Bjørling
2018-07-06 17:38 ` [PATCH 1/2] null_blk: move shared definitions to header file Matias Bjørling
2018-07-06 17:38 ` [PATCH 2/2] null_blk: add zone support Matias Bjørling
2018-07-06 17:45 ` [PATCH 0/2] null_blk: " Laurence Oberman
2018-07-09 7:54 ` Matias Bjørling
2018-07-09 16:34 ` Jens Axboe
2018-07-10 0:05 ` Bart Van Assche
2018-07-10 14:46 ` Jens Axboe
2018-07-10 16:47 ` Bart Van Assche
2018-07-10 18:45 ` Jens Axboe
2018-07-10 18:49 ` Bart Van Assche [this message]
2018-07-10 18:51 ` Jens Axboe
2018-08-09 20:51 ` Zoned block device support for fio (was: [PATCH 0/2] null_blk: zone support) Bart Van Assche
2018-08-09 21:03 ` Zoned block device support for fio Jens Axboe
2018-08-15 18:07 ` Bart Van Assche
2018-07-07 2:54 ` [PATCH 0/2] null_blk: zone support Jens Axboe
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).