From: Jens Axboe <axboe@kernel.dk>
To: Suresh Dhanarajan <sureshdrajan@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: Running fio with offset Increment option
Date: Wed, 02 May 2012 14:12:41 +0200 [thread overview]
Message-ID: <4FA124B9.8050505@kernel.dk> (raw)
In-Reply-To: <CAN8qX8a4=a4hBkuB54MGV3_+=+wrPVae6oN6Hh=H-ZQt+0ewyA@mail.gmail.com>
On 04/28/2012 09:09 PM, Suresh Dhanarajan wrote:
> Hi Jens,
>
> I verified the offsets by using the write_io_log switch.
> when i use offset increment without patch the offset are incremented
> and not reset to zero after stone wall.
> when i use with patch the offset resets to zero after stone wall.
> I hope you are testing with the patch.
> If it is so this what the behavior iam also seeing.
I'm puzzled. Did a full test here now, with the patch. Simple job:
[global]
ioengine=null
bs=1k
size=10m
offset_increment=1m
numjobs=2
write_iolog=log
[job1]
rw=read
[job2]
stonewall
rw=read
using both the write_iolog and --debug=io, I verified that job1 has two
files, one starts at 0M the next at 1M. job2 has two files, one starts
at 0M the next at 1M. If I remove the stonewall, job1 has 0M/1M and job
has 2M/3M.
That certainly looks like it's working to me. I think you need to check
and double check that you are indeed using a patched version. And note
that write_iolog will _append_ to an existing log file. Perhaps you are
looking at an earlier entry set?
--
Jens Axboe
prev parent reply other threads:[~2012-05-02 12:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 23:48 Running fio with offset Increment option Suresh Dhanarajan
2012-04-14 15:23 ` Jens Axboe
2012-04-14 15:29 ` Jens Axboe
2012-04-16 23:15 ` Suresh Dhanarajan
2012-04-17 6:30 ` Jens Axboe
2012-04-18 21:37 ` Suresh Dhanarajan
2012-04-19 5:47 ` Jens Axboe
2012-04-19 19:32 ` Suresh Dhanarajan
2012-04-20 6:27 ` Jens Axboe
2012-04-28 19:09 ` Suresh Dhanarajan
2012-05-02 12:12 ` 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=4FA124B9.8050505@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=sureshdrajan@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