From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: blktrace vs ftrace
Date: Fri, 3 Feb 2012 01:15:53 +0700 [thread overview]
Message-ID: <CAGdaadb_SQimEp3O_iH+LpFSutEkPek-t0Y2bVc=FuWU8ZqvLg@mail.gmail.com> (raw)
In-Reply-To: <4F2A6357.3060805@gmail.com>
On Thu, Feb 2, 2012 at 17:20, Matthias Brugger
<matthias.bgg@googlemail.com> wrote:
> Hi all,
>
> I'm trying to analize I/O behavior of Qemu on the host.
what is your complete command to invoke Qemu?
sometimes Qemu's I/O behaviour can be modified by certain parameter.
All I know recent Qemu release (>= 1.x) use iothread by default, which
might explain your 4 threads reads.
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
next prev parent reply other threads:[~2012-02-02 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 10:20 blktrace vs ftrace Matthias Brugger
2012-02-02 18:15 ` Mulyadi Santosa [this message]
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='CAGdaadb_SQimEp3O_iH+LpFSutEkPek-t0Y2bVc=FuWU8ZqvLg@mail.gmail.com' \
--to=mulyadi.santosa@gmail.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).