Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "phillip.a.chen@seagate.com" <phillip.a.chen@seagate.com>
Cc: "sitsofe@gmail.com" <sitsofe@gmail.com>,
	Kris Davis <Kris.Davis@wdc.com>,
	Jason Jorgensen <jason.jorgensen@wdc.com>,
	"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: ZBC/FLEX FIO addition ideas
Date: Fri, 23 Mar 2018 17:35:33 +0000	[thread overview]
Message-ID: <1521826532.2535.9.camel@wdc.com> (raw)
In-Reply-To: <CAODBMznZzLuO5HzrqJ0VPcG0eJ02oK1-K57dFOtDYbFrEEz4Gg@mail.gmail.com>

On Fri, 2018-03-23 at 11:30 -0600, Phillip Chen wrote:
> I've been trying out the ZBC changes with a few drives and workloads,
> and the only limitation I've found so far is that random write
> workloads with a queue depth > 1 seem to write beyond the write
> pointer. This isn't particularly surprising, but I wanted to double
> check if this is an expected limitation, and if so, are there plans to
> support queued random writes in the future? Other than that, the
> changes seem to be working just as advertised. I think your zone
> management system will make writing a zone random workload fairly
> straightforward. Thank you for the update!

Hello Phillip,

That is unintended behavior. A fix is ready and passes my own tests. I'm also
working on implementing additional functionality, namely to make it possible
to specify the maximum number of open zones when using fio to test an SMR
drive. I will let you know once all new functionality passes my tests.

Bart.





      reply	other threads:[~2018-03-23 17:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-06 18:59 ZBC/FLEX FIO addition ideas Phillip Chen
2018-03-15 16:15 ` Kris Davis
2018-03-15 16:30   ` Sitsofe Wheeler
2018-03-15 16:43     ` Bart Van Assche
2018-03-15 18:06       ` Phillip Chen
2018-03-15 18:38         ` Bart Van Assche
2018-03-15 19:40           ` Phillip Chen
2018-03-15 21:01             ` Bart Van Assche
2018-03-17  7:55       ` Sitsofe Wheeler
2018-03-20  2:21         ` Bart Van Assche
2018-03-23 17:30           ` Phillip Chen
2018-03-23 17:35             ` Bart Van Assche [this message]

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=1521826532.2535.9.camel@wdc.com \
    --to=bart.vanassche@wdc.com \
    --cc=Kris.Davis@wdc.com \
    --cc=fio@vger.kernel.org \
    --cc=jason.jorgensen@wdc.com \
    --cc=phillip.a.chen@seagate.com \
    --cc=sitsofe@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