Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: DongJin Lee <dongjin.lee@auckland.ac.nz>
Cc: Michael O'Sullivan <michael.osullivan@auckland.ac.nz>,
	fio@vger.kernel.org
Subject: Re: Using offsets in fio
Date: Tue, 27 Apr 2010 08:54:55 +0200	[thread overview]
Message-ID: <20100427065454.GY27497@kernel.dk> (raw)
In-Reply-To: <k2v8baae1371004262349sb41985e9i73f4d3a2e42aca7c@mail.gmail.com>

On Tue, Apr 27 2010, DongJin Lee wrote:
> So for example, you'd expect, for example,
> at the end of 1TB position (1073741824 bytes) the offset is to be 1073741824
> ?

1073741824 byte offset would be 1GB.

> and similarly for end of 2TB position, the offset would be the twice?

Yeah, there's no magic there, it's simply a byte offset where the IO
will take place.

-- 
Jens Axboe


      reply	other threads:[~2010-04-27  6:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27  0:19 Using offsets in fio Michael O'Sullivan
2010-04-27  6:42 ` Jens Axboe
2010-04-27  6:49   ` DongJin Lee
2010-04-27  6:54     ` 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=20100427065454.GY27497@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=dongjin.lee@auckland.ac.nz \
    --cc=fio@vger.kernel.org \
    --cc=michael.osullivan@auckland.ac.nz \
    /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