From: Jens Axboe <axboe@kernel.dk>
To: Jon Tango <cheerios123@outlook.com>, fio@vger.kernel.org
Subject: Re: Limit LBA Range
Date: Mon, 29 Sep 2014 15:38:19 -0600 [thread overview]
Message-ID: <5429D14B.5030908@kernel.dk> (raw)
In-Reply-To: <BLU402-EAS37786FC6E4480886241B03CE0BA0@phx.gbl>
On 2014-09-29 15:37, Jon Tango wrote:
>
> On 2014-09-29 15:10, Jon Tango wrote:
>> I include both of those commands, in addition to size=745g, and it
>> seems to be conducting the workload over the entire LBA range. Is this
>> the correct combination of the three parameters? Here is the test script:
>
> When you explicitly set size=745G, the range is 0..745G as previously
> specified.
>
> --
> Jens Axboe
>
> --
> So it would be both time_based and limited to 745G as well? The workload
> will continue to run even if over 745GB of data is written, but only to the
> 0..745GB range?
>
> size=745G
> time_based
> runtime=4h
Yes and yes
--
Jens Axboe
next prev parent reply other threads:[~2014-09-29 21:38 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 [this message]
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
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=5429D14B.5030908@kernel.dk \
--to=axboe@kernel.dk \
--cc=cheerios123@outlook.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.