Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Lakshmi <sendtold@gmail.com>, fio@vger.kernel.org
Subject: Re: Qn on setting ioengine on Replay job
Date: Tue, 08 Apr 2014 13:44:26 -0600	[thread overview]
Message-ID: <5344519A.9020607@kernel.dk> (raw)
In-Reply-To: <53444A86.3030904@kernel.dk>

On 04/08/2014 01:14 PM, Jens Axboe wrote:
> On 04/08/2014 10:39 AM, Lakshmi wrote:
>> Hi Jens,
>>
>>    Is it possible to set the ioengine and iodepth on a replay job?
>> Would it have any effect on the replay jobs? I tried setting as below,
>> but didnt see any change. So wanted to make sure if what I am doing is
>> valid.
>>
>> [global]
>> replay_no_stall=1
>> ioengine=posixaio
>> buffered=0
>> iodepth=6
>>
>> [job1]
>> read_iolog=/home/file_3080658.bin
>
> The ioengine will always work, the iodepth should work as well. blktrace
> loading doesn't actually set the iodepth, so it should run at depth 1
> unless you tell it otherwise. That should be fixed up, actually.
>
> That said, you wont see higher depth than the job itself has done. The
> depth will be naturally limited by the events in that trace. However, if
> a lower depth is set, then that should be enforced (since fio is forced
> to wait on IO if it runs out of IO buffers).

Added a patch to probe the depth from the blktrace file. So should now 
set the detected depth, if it can.

-- 
Jens Axboe



      reply	other threads:[~2014-04-08 19:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08 16:39 Qn on setting ioengine on Replay job Lakshmi
2014-04-08 19:14 ` Jens Axboe
2014-04-08 19:44   ` 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=5344519A.9020607@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=sendtold@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