From: Jens Axboe <qemu@kernel.dk>
To: Christian MICHON <christian.michon@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [patch] non-blocking disk IO
Date: Tue, 4 Oct 2005 14:22:55 +0200 [thread overview]
Message-ID: <20051004122254.GO3511@suse.de> (raw)
In-Reply-To: <46d6db660510040419p475ed971w3a452c0cebbfa13f@mail.gmail.com>
On Tue, Oct 04 2005, Christian MICHON wrote:
> hmmm....
>
> the static binary crashes, the one with ptreadGC2.dll is ok.
>
> What I tried to measure, on windows host, kqemu-0.7.2
> loaded, was:
> (1) tar -jxf linux-2.6.10.tar.bz2
> (2) make allnoconfig; make
>
> I confirm ~18% speed improvement in case (1), but no change
> more or less for case (2). I believe maybe someone with a
> windows host SMP could get different figures. If so, please
> update these accordingly and let the list know.
>
> Indeed, threading on a busy single CPU doesn't make it faster.
That's not quite true. The io thread basically takes no real CPU, but it
often has to wait for io to become available. So even (especially!) for
a single cpu system, you definitely want to make sure that blocking io
doesn't eat away cpu cycles from a cpu bound case like the compile.
If you did the kernel compile with a hot disk cache, I'm not surprised
you're not seeing a performance benefit of the non-blocking io patch.
Even for a cold cache compile it will generally be cpu bound.
--
Jens Axboe
next prev parent reply other threads:[~2005-10-04 12:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-03 6:49 [Qemu-devel] [patch] non-blocking disk IO John Coiner
2005-10-03 7:09 ` Magnus Damm
2005-10-03 9:57 ` Elefterios Stamatogiannakis
2005-10-03 12:58 ` Christian MICHON
2005-10-04 7:17 ` John Coiner
2005-10-04 7:46 ` Christian MICHON
2005-10-04 8:52 ` Elefterios Stamatogiannakis
2005-10-04 9:35 ` Christian MICHON
2005-10-04 11:19 ` Christian MICHON
2005-10-04 12:22 ` Jens Axboe [this message]
2005-10-04 13:14 ` John Coiner
2005-10-04 13:20 ` Christian MICHON
2005-10-03 13:58 ` Jens Axboe
2005-10-03 22:29 ` John Coiner
2005-10-04 6:41 ` Jens Axboe
2005-10-04 1:35 ` Troy Benjegerdes
2005-10-04 3:25 ` John Coiner
2005-10-04 3:49 ` Henrik Nordstrom
2005-10-04 5:24 ` Troy Benjegerdes
2005-10-04 6:44 ` Jens Axboe
2005-10-03 18:33 ` Fabrice Bellard
2005-10-04 20:40 ` Brad Campbell
2005-10-04 23:03 ` John Coiner
2005-10-05 11:27 ` Brad Campbell
2005-10-05 14:28 ` Troy Benjegerdes
2005-11-28 22:41 ` Ryan Rempel
-- strict thread matches above, loose matches on Subject: below --
2005-10-03 12:41 John Coiner
2005-10-04 1:34 ` Troy Benjegerdes
2005-10-04 3:16 ` John Coiner
2005-10-04 14:26 ` Troy Benjegerdes
2005-10-04 22:11 ` John Coiner
2005-10-05 3:17 ` Troy Benjegerdes
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=20051004122254.GO3511@suse.de \
--to=qemu@kernel.dk \
--cc=christian.michon@gmail.com \
--cc=qemu-devel@nongnu.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 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.