From: Jens Axboe <axboe@kernel.dk>
To: Mansour Shafaei Moghaddam <mansoor.shafaei@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: A probable minor mistake in HOWTO page
Date: Fri, 24 Apr 2015 11:16:36 -0600 [thread overview]
Message-ID: <553A7A74.6020306@kernel.dk> (raw)
In-Reply-To: <CAGGT8x6QUt9kn51vpDFn8RdZxn-oJosW1OJ6daZQzUorymRXmA@mail.gmail.com>
On 04/24/2015 11:10 AM, Mansour Shafaei Moghaddam wrote:
> But I still think that the time is not relative to anything except the
> beginning of the job i.e., 0:00:00. I again tried running the
> following trace:
>
> io version 2 iolog
> /dev/sde add
> /dev/sde open
> /dev/sde read 1499999997952 16384
> /dev/sde read 4499992682496 16384
> /dev/sde read 4499992682496 16384
> /dev/sde wait 3000 16384
> /dev/sde read 4499992682496 16384
> /dev/sde read 4499992682496 16384
> /dev/sde read 4499992682496 16384
> /dev/sde wait 5000 16384
> /dev/sde read 1499999997952 16384
> /dev/sde read 4499993485312 16384
> /dev/sde read 4499993485312 16384
> /dev/sde read 4499993485312 16384
> /dev/sde read 4499993485312 16384
> /dev/sde read 4499993485312 16384
> /dev/sde close
>
> with the job file shown below:
>
>
> [global]
> log_offset=1
> direct=1
> ioengine=sync
> [read-phase]
> write_lat_log=test
> read_iolog=testtrace
>
> Here is what I see in the clat file:
>
>
> 22, 22165, 0, 16384, 1499999997952
> 48, 25752, 0, 16384, 4499992682496
> 58, 10044, 0, 16384, 4499992682496
> 2907, 8123, 0, 16384, 4499992682496
> 2917, 10077, 0, 16384, 4499992682496
> 2927, 10002, 0, 16384, 4499992682496
> 4918, 18610, 0, 16384, 1499999997952
> 4942, 24021, 0, 16384, 4499993485312
> 4952, 10018, 0, 16384, 4499993485312
> 4962, 10017, 0, 16384, 4499993485312
> 4972, 10030, 0, 16384, 4499993485312
> 4982, 10029, 0, 16384, 4499993485312
>
> As you can see submission times are like
> (22,....,2907,.....,4918,...). So the given value as offset is being
> interpreted as absolute delay. In other words it is the time stamp for
> the IO right after that. If it is less than the current time of the
> job it will be ignored. Otherwise, it will be applied.
Yeah, I was too quick, looking at the code, on reading the log, we store
offset in delay directly:
if (rw == DDIR_WAIT) {
ipo->delay = offset;
} else {
and on retrieval, we factor in the 'td' time offset as an absolute delay.
--
Jens Axboe
next prev parent reply other threads:[~2015-04-24 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 17:23 A probable minor mistake in HOWTO page Mansour Shafaei Moghaddam
2015-04-24 16:46 ` Jens Axboe
2015-04-24 17:10 ` Mansour Shafaei Moghaddam
2015-04-24 17:16 ` Jens Axboe [this message]
2015-04-24 17:18 ` Mansour Shafaei Moghaddam
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=553A7A74.6020306@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=mansoor.shafaei@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 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.