Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Andrey Kuzmin <andrey.v.kuzmin@gmail.com>,
	Jon Tango <cheerios123@outlook.com>
Cc: Sitsofe Wheeler <sitsofe@gmail.com>, fio@vger.kernel.org
Subject: Re: Limit LBA Range
Date: Tue, 30 Sep 2014 08:47:06 -0600	[thread overview]
Message-ID: <542AC26A.7030608@kernel.dk> (raw)
In-Reply-To: <CANvN+ekYFU7=Fyq3Owv9Z-E8ZSR3xHXru3LVSCseCoqJJpjAYg@mail.gmail.com>

On 2014-09-30 02:57, Andrey Kuzmin wrote:
> The same thing could be done by partitioning the SSD in the operating
> system with the desired partition size, and then running a time-based
> fio job against the partition.
>
> Basically, fio options offset/size should yield the same net result,
> but I'm always unsure on what is the actual effect of mixing size and
> time_based in a single job, and whether fio will wrap around the
> specified size to the specified offset if the job is time-based. HOWTO
> could have used some clarification on size/time_based interaction.

The HOWTO currently states:

time_based      If set, fio will run for the duration of the runtime
                 specified even if the file(s) are completely read
                 or written. It will simply loop over the same workload
                 as many times as the runtime allows.

Especially the last sentence should make it clear, that it will simply 
run the specified workload over and over until the time has passed. I'd 
welcome changes to make that clearer, if it doesn't get the point across.

-- 
Jens Axboe



  parent reply	other threads:[~2014-09-30 14:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-29  3:28 Limit LBA Range Jon Tango
2014-09-29 19:33 ` Jens Axboe
2014-09-29 20:46   ` Jon Tango
2014-09-29 20:59     ` Jens Axboe
2014-09-29 21:10       ` Jon Tango
2014-09-29 21:21         ` Jens Axboe
2014-09-29 21:37           ` Jon Tango
2014-09-29 21:38             ` Jens Axboe
2014-09-30  2:23         ` Sitsofe Wheeler
2014-09-30  2:49           ` Jens Axboe
2014-09-30  3:18             ` Sitsofe Wheeler
2014-09-30  4:57             ` Jon Tango
2014-09-30  6:23               ` Sitsofe Wheeler
2014-09-30  6:34                 ` Jon Tango
2014-09-30  7:36                   ` Sitsofe Wheeler
2014-09-30  7:56                     ` Jon Tango
2014-09-30 13:07                       ` Sitsofe Wheeler
2014-09-30 21:17                         ` Sitsofe Wheeler
2014-09-30 14:44                       ` Jens Axboe
2014-09-30  8:57                     ` Andrey Kuzmin
2014-09-30  9:14                       ` Jon Tango
2014-09-30  9:17                         ` Andrey Kuzmin
2014-09-30 14:48                           ` Jens Axboe
2014-09-30 14:47                       ` Jens Axboe [this message]
2014-10-01 16:33                         ` Andrey Kuzmin
2014-09-29 21:01   ` Jon Tango

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=542AC26A.7030608@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=andrey.v.kuzmin@gmail.com \
    --cc=cheerios123@outlook.com \
    --cc=fio@vger.kernel.org \
    --cc=sitsofe@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox