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:48:18 -0600 [thread overview]
Message-ID: <542AC2B2.1070801@kernel.dk> (raw)
In-Reply-To: <CANvN+eme+6YiF8oNVDN0juq=8xLmf8Cn3FXjcgf5z26UVHW_zw@mail.gmail.com>
On 2014-09-30 03:17, Andrey Kuzmin wrote:
> On Tue, Sep 30, 2014 at 1:14 PM, Jon Tango <cheerios123@outlook.com> 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.
>>
>> Regards,
>> Andrey
>>
>> On Sep 30, 2014 11:41 AM, "Sitsofe Wheeler" <sitsofe@gmail.com> wrote:
>>>
>>> On 30 September 2014 07:34, Jon Tango <cheerios123@outlook.com> wrote:
>>>>
>>>> The taskfile is this:
>>>
>>> I should have been more specific - you need to show both the _vdbench_
>>> parameter file that you are comparing to in addition to showing your
>>> fio job file.
>>>
>>> --
>>> Sitsofe |http://sucs.org/~sits/
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe fio" in the
>>> body of a message tomajordomo@vger.kernel.org More majordomo info at
>>> http://vger.kernel.org/majordomo-info.html
>> --
>> To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>> I'm really wanting to avoid the filesystem, they create so much interference. I am focusing on just testing the raw device :)
>
> I'm not sure why a filesystem should be involved in partitioning, that
> happens at the raw device level.
I think there's some limitation in Windows that doesn't allow partition
raw IO. I may be mistaken.
But I agree, partition would work. But just limiting the LBA range with
size= will do the same job.
--
Jens Axboe
next prev parent reply other threads:[~2014-09-30 14:48 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 [this message]
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=542AC2B2.1070801@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