Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Carl Zwanzig <cpz@coraid.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Generating almost-sequential traffic
Date: Thu, 27 Jun 2013 21:28:28 +0200	[thread overview]
Message-ID: <20130627192828.GH25599@kernel.dk> (raw)
In-Reply-To: <A7A1D348E34E024BBC74480FB93A2EAB039F2F@DAGN05A-E6.exg6.exghost.com>

On Thu, Jun 27 2013, Carl Zwanzig wrote:
> > From: Jens Axboe [mailto:axboe@kernel.dk]
> > Sent: Thursday, June 27, 2013 2:01 AM
> 
> > See percentage_random in the man page (or --cmdhelp=percentage_random)
> 
> In the tests I'm running, the sequence has to continue essentially
> uninterrupted with the occasional drop/transposition, but it can't
> contain LBAs that are wildly off. So '1 2 3 (4) 5 6' or '1 2 3 (5 4)
> 6' are good, '1 2 3 9999 4 5 6' is not. They trigger different
> specific behaviors in some hard drives.
> 
> Is there a good place in the code to insert this sort or thing?

I would look at the profile support in fio. That allows you to hook into
io_u.c:get_next_offset(), which is where fio decides what the next
offset should be. If a profile defines ops->fill_io_u(), then that is
called instead. That gives you absolute control of the IO pattern,
without having to modify core fio code.

-- 
Jens Axboe



      reply	other threads:[~2013-06-27 19:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-26 22:31 Generating almost-sequential traffic Carl Zwanzig
2013-06-27  9:01 ` Jens Axboe
2013-06-27 17:41   ` Carl Zwanzig
2013-06-27 19:28     ` 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=20130627192828.GH25599@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=cpz@coraid.com \
    --cc=fio@vger.kernel.org \
    /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