Flexible I/O Tester development
 help / color / mirror / Atom feed
* Specify range and distribution of accesses
@ 2016-02-26 20:53 Jeff Furlong
  2016-02-27  9:14 ` Andrey Kuzmin
  2016-03-03 16:16 ` Jens Axboe
  0 siblings, 2 replies; 13+ messages in thread
From: Jeff Furlong @ 2016-02-26 20:53 UTC (permalink / raw)
  To: fio@vger.kernel.org

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.

Regards,
Jeff

Western Digital Corporation (and its subsidiaries) E-mail Confidentiality Notice & Disclaimer:

This e-mail and any files transmitted with it may contain confidential or legally privileged information of WDC and/or its affiliates, and are intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited. If you have received this e-mail in error, please notify the sender immediately and delete the e-mail in its entirety from your system.


^ permalink raw reply	[flat|nested] 13+ messages in thread

end of thread, other threads:[~2016-03-12  2:07 UTC | newest]

Thread overview: 13+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox