kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: matthias.bgg@googlemail.com (Matthias Brugger)
To: kernelnewbies@lists.kernelnewbies.org
Subject: blktrace vs ftrace
Date: Thu, 02 Feb 2012 11:20:07 +0100	[thread overview]
Message-ID: <4F2A6357.3060805@gmail.com> (raw)

Hi all,

I'm trying to analize I/O behavior of Qemu on the host.

I used blktrace and the blk tracer for ftrace but I see different I/O 
behavior.
I use 4 threads in the VM each reading sequentially a file. Readahead is 
turned off. With blktrace reads are transmitted in a sequential way, 
which means the next read will be executed when the first one has 
completed. In comparison with ftrace, up to 4 reads are issued to the 
disk in parallel.

I suppose the different behaviors are due to the overhead introduced by 
the tracers.
My doubt is, which tracer has less influence on the I/O behaviour and 
therefore reflects the system behaviour without tracing.

Thanks a lot,
Matthias

---
http://motzblog.wordpress.com/

             reply	other threads:[~2012-02-02 10:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-02 10:20 Matthias Brugger [this message]
2012-02-02 18:15 ` blktrace vs ftrace Mulyadi Santosa
2012-02-02 19:06   ` Matthias Brugger
2012-02-03  5:59     ` Mulyadi Santosa
2012-02-08 10:59       ` Matthias Brugger
2012-02-08 17:04         ` Mulyadi Santosa

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=4F2A6357.3060805@gmail.com \
    --to=matthias.bgg@googlemail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).