All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Jeff Furlong <jeff.furlong@hgst.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Specify range and distribution of accesses
Date: Thu, 3 Mar 2016 09:16:03 -0700	[thread overview]
Message-ID: <20160303161603.GB22164@kernel.dk> (raw)
In-Reply-To: <BN3PR0401MB145783CB3B39ADEEAED39523F7A70@BN3PR0401MB1457.namprd04.prod.outlook.com>

On Fri, Feb 26 2016, Jeff Furlong wrote:
> Hi All,
> I'm looking for a method to distribute access to certain ranges of a
> block device.  For example, the JESD219 workload
> (http://www.jedec.org/sites/default/files/docs/JESD219.pdf) specifies 
> 
> The workload shall be distributed across the SSD such that the following is achieved:
> 1) 50% of accesses to first 5% of user LBA space (LBA group a)
> 2) 30% of accesses to next 15% of user LBA space (LBA group b)
> 3) 20% of accesses to remainder of user LBA space (LBA group c)
> 
> I do not currently see any fio options to allow such usage.  Perhaps
> if --size or --iosize is updated to allow ranges/distributions, it may
> be possible?
> 
> The JESD219 workload also specifies a distribution of block sizes,
> which can already be accomplished in fio with --bssplit, such as
> --bssplit=4k/10:64k/50:32k/40.  Perhaps extending that usage to --size
> or --iosize may solve the issue?
> 
> The above link for the JESD219 workload includes a vdbench script to
> produce the desired workload, but I'm hesitant to think that vdbench
> does something that fio cannot.  Has anyone been able to specify
> ranges and distributions of accesses in any other way?  Thanks.

There's no straight forward way to do that, I'm afraid. Might be
possible to do with a somewhat convoluted use of the existing
options. Would be a useful addition, however, to be able to do this in a
logical manner. I'll think about it a bit, would require some
abstraction around zoning of a fio_file.

-- 
Jens Axboe



      parent reply	other threads:[~2016-03-03 16:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26 20:53 Specify range and distribution of accesses Jeff Furlong
2016-02-27  9:14 ` Andrey Kuzmin
2016-03-03 16:18   ` Jens Axboe
2016-03-03 20:04     ` Jens Axboe
2016-03-07 20:46       ` Jeff Furlong
2016-03-07 21:02         ` Andrey Kuzmin
2016-03-07 21:08           ` Jens Axboe
2016-03-08  2:41           ` Jens Axboe
2016-03-07 21:08         ` Jens Axboe
2016-03-07 21:19         ` Elliott, Robert (Persistent Memory)
2016-03-07 21:45           ` Jens Axboe
2016-03-12  2:07       ` Vladislav Bolkhovitin
2016-03-03 16:16 ` Jens Axboe [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=20160303161603.GB22164@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=jeff.furlong@hgst.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.