From: Akira Hayakawa <ruby.wktk@gmail.com>
To: andrey.v.kuzmin@gmail.com
Cc: fio@vger.kernel.org
Subject: Re: [Question] How to perform stride access?
Date: Wed, 24 Sep 2014 17:35:03 +0900 [thread overview]
Message-ID: <54228237.5000805@gmail.com> (raw)
In-Reply-To: <CANvN+enrUD45Zp1CJKQ3kxQncHLyhp7hE1jr4AnzRD65oDTUvg@mail.gmail.com>
Thanks Andrey,
However, I don't think I still have a problem.
I modified the command
From:
>> fio --name=test --filename=#{dev.path} --rw=write --ioengine=libaio --direct=1 --io_limit=32M --size=100% --ba=4k --bs=512
To:
fio --name=test --filename=#{dev.path} --rw=write:4k --ioengine=libaio --direct=1 --io_limit=32M --bs=512
The result is the runtime is too short.
I guess fio stops as soon as it reaches the end of the device.
However, I want it to repeat over and over again until io_limit is fully consumed.
Note that the device is smaller than 32M (it is only 508B).
So, it should repeat more than 60 times.
How can I repeat the workload?
Or,
Building hand-made random map would suffice, I guess.
- Akira
On 9/23/14 11:05 PM, Andrey Kuzmin wrote:
> Offset modifier under rw= should do the trick, consult
> https://github.com/axboe/fio/blob/master/HOWTO for details.
>
> Best regards,
> Andrey
> Regards,
> Andrey
>
>
> On Tue, Sep 23, 2014 at 5:47 PM, Akira Hayakawa <ruby.wktk@gmail.com> wrote:
>> Hi,
>>
>> I want to perform stride write access to a block device but
>> I don't have a clue how I can do that.
>>
>> What I want to do is to perform a stride access that
>> each write size is 1 sector and 7 sectors are apart between each writes.
>> (i.e. Only the first sector of each 4KB block)
>>
>> For example,
>> 0, 8, 16, 24, 32, ...
>>
>> And, it repeat over the device until certain amount of writes are accomplished.
>> In my case, amount of 32MB to 508KB device.
>>
>> I consider the command below works like as I want but it doesn't actually.
>> Instead, it looks performing ordinary 512KB seq write.
>> fio --name=test --filename=#{dev.path} --rw=write --ioengine=libaio --direct=1 --io_limit=32M --size=100% --ba=4k --bs=512
>>
>> My questions are:
>> 1) How to perform stride write access in fio?
>> 2) If fio is not a appropriate tool for this purpose, easy to fix?
>> Or do you recommend other tool?
>>
>> - Akira
>> --
>> 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
next prev parent reply other threads:[~2014-09-24 8:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 13:47 [Question] How to perform stride access? Akira Hayakawa
2014-09-23 14:05 ` Andrey Kuzmin
2014-09-24 8:35 ` Akira Hayakawa [this message]
[not found] ` <CANvN+emPbk+MwwNoABs-rdWdJbn+JD+O0GVAGftR4w7mNVndcg@mail.gmail.com>
2014-09-24 9:28 ` Akira Hayakawa
2014-09-24 9:52 ` Sitsofe Wheeler
2014-09-24 9:58 ` Akira Hayakawa
2014-09-24 21:22 ` Sitsofe Wheeler
2014-09-28 2:24 ` Jens Axboe
2014-09-28 10:32 ` Sitsofe Wheeler
2014-09-28 10:36 ` Sitsofe Wheeler
2014-09-28 14:24 ` Jens Axboe
2014-09-28 15:08 ` Jens Axboe
2014-09-28 19:44 ` Sitsofe Wheeler
2014-09-28 22:13 ` Jens Axboe
2014-09-29 5:42 ` Sitsofe Wheeler
2014-09-29 7:41 ` Sitsofe Wheeler
2014-09-30 1:23 ` Akira Hayakawa
2014-09-30 2:21 ` Jens Axboe
2014-10-05 7:15 ` Akira Hayakawa
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=54228237.5000805@gmail.com \
--to=ruby.wktk@gmail.com \
--cc=andrey.v.kuzmin@gmail.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