qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christian MICHON <christian.michon@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [patch] non-blocking disk IO
Date: Tue, 4 Oct 2005 13:19:18 +0200	[thread overview]
Message-ID: <46d6db660510040419p475ed971w3a452c0cebbfa13f@mail.gmail.com> (raw)
In-Reply-To: <46d6db660510040235i547ea37aw33965dbe77c0a390@mail.gmail.com>

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.
A kernel compilation with kqemu makes full use of the CPU. :(

I think we'll benefit mostly when copying files or setup OSes when
the CPU is quite in IDLE state. I've no figures without kqemu yet.

At least, it's a good start for speed improvement.
Thanks for the patch! :)

On 10/4/05, Christian MICHON <christian.michon@gmail.com> wrote:
> indeed, this was a quick and dirty hack :)
> I just managed to compile pthreadGC2 statically...
> pthread.h has to be modified to include extra
> PTW32_STATIC_LIB info, like this:
>
> #define PTW32_VERSION 2,6,0,0
> #define PTW32_VERSION_STRING "2, 6, 0, 0\0"
> #define PTW32_STATIC_LIB 1
>
> I'll test it later today and will report realistic benchmarks
> on windows hosts.
>

--
Christian

  reply	other threads:[~2005-10-04 11:23 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 [this message]
2005-10-04 12:22             ` Jens Axboe
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=46d6db660510040419p475ed971w3a452c0cebbfa13f@mail.gmail.com \
    --to=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 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).