qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Leonardo E. Reiter" <lreiter@win4lin.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Network Performance between Win Host and Linux
Date: Wed, 12 Apr 2006 10:31:31 -0400	[thread overview]
Message-ID: <443D0F43.7050402@win4lin.com> (raw)
In-Reply-To: <6fe044190604111536k944383o99ab27411d3864db@mail.gmail.com>

On an additional note, Windows host users may want to try moving the 
arbitrary Sleep() in main_loop_wait() to the end of the function, and 
making that conditional if there are no I/O events pending.  Otherwise, 
there is a fixed penalty and this does not take advantage of Ken's new 
patch to avoid the delay if there are pending slirp requests for 
example.  When I have some time I will see if there is a better way to 
multiplex poll in Windows, so that you can use something like select() 
but still get interrupted.  There might for example be something 
relevant in the newer winsock libraries (i.e. V2), but of course it has 
to be general enough to work on any type of fd.

I apologize but I have not yet been able to successfully build QEMU on 
Windows, even after mucking with the mingw stuff.  I probably need to 
spend more time on it at some point.  But if anyone is using Windows and 
can compile QEMU from source, you can try moving the Sleep to see if 
that helps, especially after applying Ken's new patches.  Actually 
Kazu's patch for TAP performance addresses this for TAP for example, so 
it should be easy to adapt to slirp... the code is in very close proximity.

- Leo Reiter

Kenneth Duda wrote:
> The "qemu-slirp-performance" patch contains three improvements to qemu
> slirp networking performance.  Booting my virtual machine (which
> NFS-mounts its root filesystem from the host) has been accelerated by
> 8x, from over 5 minutes to 40 seconds.  TCP throughput has been
> accelerated from about 2 megabytes/sec to 9 megabytes/sec, in both
> directions (measured using a simple python script).  The system is
> subjectively more responsive (for activities such as logging in or
> running simple python scripts).

-- 
Leonardo E. Reiter
Vice President of Product Development, CTO

Win4Lin, Inc.
Virtual Computing from Desktop to Data Center
Main: +1 512 339 7979
Fax: +1 512 532 6501
http://www.win4lin.com

      parent reply	other threads:[~2006-04-12 14:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-11 17:20 [Qemu-devel] Network Performance between Win Host and Linux Kenneth Duda
2006-04-11 17:28 ` Paul Brook
2006-04-11 17:49   ` Kenneth Duda
2006-04-11 18:19     ` Helmut Auer
2006-04-12  2:10       ` Kazu
2006-04-11 20:40     ` Leonardo E. Reiter
2006-04-11 21:46       ` Kenneth Duda
2006-04-11 21:58         ` Leonardo E. Reiter
2006-04-11 22:42           ` Kenneth Duda
2006-04-11 21:00     ` Leonardo E. Reiter
2006-04-11 22:36 ` [Qemu-devel] " Kenneth Duda
2006-04-12 14:04   ` Leonardo E. Reiter
2006-04-12 18:19     ` Kenneth Duda
2006-04-12 18:26       ` Leonardo E. Reiter
2006-04-12 14:31   ` Leonardo E. Reiter [this message]

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=443D0F43.7050402@win4lin.com \
    --to=lreiter@win4lin.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).