All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Lakshmi <sendtold@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: No IOPS reported when "REPLAY_NO_STALL" is not set
Date: Fri, 11 Apr 2014 09:47:29 -0600	[thread overview]
Message-ID: <53480E91.2000805@kernel.dk> (raw)
In-Reply-To: <CAEyTGCfybCJ-EoDMouX5puAnicpnk_MVtm+H4JLSzgNAYPQSjw@mail.gmail.com>

On 04/11/2014 09:36 AM, Lakshmi wrote:
> Hi Jens,
>
> Thanks for the command. I was looking for something like this.
> However, I am still confused on the time stamp calculation.
> My Binary file had the starting time as "26.040173218 seconds" , but
> with the below command,
>
> cat file_54657438_1000lines.bin | blkparse - | less
>
>    8,0   60        0     0.000000000 54657438  Q   R 24014152 + 8 [(null)]
>    8,0   60        0    66.860158593 54657438  Q   R 805379152 +8 [(null)]
>    8,0   60        0    80.644832628 54657438  Q   R 24014160 + 8 [(null)]
>
> The first line starts at 0 timestamp and then 66sec etc. I dont
> understand how the 66sec is calculated in the above blkparse command.
> Shouldnt it be 26.040173218 sec ?
>
> I do see 26.040173218 in the binary file and checked this using a
> binary viewer.Attached is the binary viewer of the file.
> Please help me understand.

If you look at the binary, the first timestamp is indeed the one you 
highlight. This then becomes the time 0, since all the other events are 
relative to this one. So 0x403a0a48cac17c2e is time 0, next timestamp is 
0x403a0a585bee8aaf, or 66860158593 nanoseconds ahead, which is 66.86s 
further ahead in time.

I don't know where you get the 26.04 from?

-- 
Jens Axboe



  reply	other threads:[~2014-04-11 15:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10 18:25 No IOPS reported when "REPLAY_NO_STALL" is not set Lakshmi
2014-04-10 22:07 ` Jens Axboe
2014-04-11 15:36   ` Lakshmi
2014-04-11 15:47     ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-04-10 17:21 No IOPS reported when "Replay_no_stall" " Lakshmi

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=53480E91.2000805@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 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.