Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: "Jenkins, Lee" <Lee.Jenkins@hp.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: I/O alignment
Date: Tue, 10 Mar 2009 20:54:08 +0100	[thread overview]
Message-ID: <20090310195408.GJ11787@kernel.dk> (raw)
In-Reply-To: <4C6CAE54C846144981BCE6F26B203FFA1CB3F68AE8@GVW1098EXB.americas.hpqcorp.net>

On Tue, Mar 10 2009, Jenkins, Lee wrote:
> Is there a way to control the alignment of I/O offsets? The HOWTO
> shows bsrange= and bs_unaligned=, but these seem to be related to the
> size of the I/O, not the offset.
> 
> In our lab testing it appears from blktrace dumps that I/Os are
> boundary-aligned based on the size of the I/O. For example, in a test
> of 64KB Random Reads all the I/O addresses were multiples of 64KB (128
> sectors). This alignment has a profound impact on I/O performance for
> certain disk array configurations. Ideally we'd like to be able to
> control the alignment to match our customers' run-time environment.

That is correct, fio will use your minimum block size as the alignment
block as well. This is needed for the random map and doing verifies, for
instance. But I see your point, being able to specifically set your
minimum alignment is indeed useful. It would have to be with the
'norandommap' option, at least that would be the easiest.

I'll add such an option for you tomorrow. Suggestions for option name
would be appreciated, I'm not very good with coming up with good names
:-)

-- 
Jens Axboe


  reply	other threads:[~2009-03-10 19:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <499e38d2.fWWZqp8SkMl4HRX/%jens.axboe@oracle.com>
2009-03-10 19:43 ` I/O alignment Jenkins, Lee
2009-03-10 19:54   ` Jens Axboe [this message]
2009-03-11  9:57     ` Jens Axboe

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=20090310195408.GJ11787@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=Lee.Jenkins@hp.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