All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Mark McLoughlin <markmc@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Alex Williamson <alex.williamson@hp.com>
Subject: [Qemu-devel] Re: Networking patches queue
Date: Wed, 10 Jun 2009 18:08:25 -0500	[thread overview]
Message-ID: <4A303CE9.6080402@us.ibm.com> (raw)
In-Reply-To: <1244583818.7164.19.camel@blaa>

Mark McLoughlin wrote:
> I've re-based the queue and pulled in Alex's rx filtering patches.
>
> I've tested the tree as follows:
>
>   - Mostly just with --enable-kvm
>
>   - F-11 host and guest
>
>   - Basic functional testing (dhcp, ping, ssh, scp) with tap, slirp, 
>     virtio-net and e1000
>
>   - Some quick host<->guest netperf benchmarks (results in Mb/s):
>
>                     | TCP TX | UDP TX | TCP RX | UDP RX
>       --------------+--------+--------+--------+-------
>       virtio before |  386   |  1545  |   190  |  410 
>              after  |  760   |  1540  |  1100  |  860*
>       e1000  before |  220   |   155  |    88  |  160
>              after  |  400   |   165  |  1255  |  180*
>
>       * - these UDP RX results show the received figures; the sent
>           figures are much higher since the host is sending so fast
>           it is overflowing the socket buffers in the guest
>
>   - Pushed it through a basic kvm-autotest run, to see if e.g. the 
>     SIGCHLD handler had side-effects not thrown up by networking tests
>
>   - Confirmed that invalid parameter and hotplug errors are working as 
>     expected after Jan's changes
>
>   - Basic testing of slirp redirs
>
>   - Basic testing of promisc, allmuti, mac table filtering etc. - Alex 
>     clearly has tested this in more detail, though
>
>   - Attempted to test old->new virtio-net migrations (given the 
>     version_id bumps), but virtio migration is still broken on HEAD
>
> Pull request below.
>   

Pulled.  Thanks.

Regards,

Anthony Liguori

  reply	other threads:[~2009-06-10 23:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28 15:19 [Qemu-devel] Networking patches queue Mark McLoughlin
2009-05-28 15:28 ` [Qemu-devel] " Anthony Liguori
2009-05-28 15:51   ` Jan Kiszka
2009-05-28 16:57     ` Mark McLoughlin
2009-05-28 20:26       ` Anthony Liguori
2009-05-28 17:01     ` Glauber Costa
2009-05-28 17:19       ` Jan Kiszka
2009-05-28 19:10       ` Jan Kiszka
2009-05-28 15:51   ` Mark McLoughlin
2009-05-28 15:56     ` Anthony Liguori
2009-05-28 16:52       ` Mark McLoughlin
2009-05-31 20:58       ` Dor Laor
2009-06-09 21:43 ` Mark McLoughlin
2009-06-10 23:08   ` Anthony Liguori [this message]
2009-06-11  1:27   ` Anthony Liguori
2009-06-11  8:34     ` Mark McLoughlin
2009-06-11  8:38   ` Gerd Hoffmann
2009-06-11  9:42     ` [Qemu-devel] [PATCH] Fix xilinx_ethlite breakage by 4f1c942b7f Jan Kiszka
2009-06-11 10:48       ` [Qemu-devel] " Mark McLoughlin
2009-06-11 11:48   ` [Qemu-devel] Re: Networking patches queue Paul Brook
2009-06-11 12:50     ` Anthony Liguori

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=4A303CE9.6080402@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=alex.williamson@hp.com \
    --cc=jan.kiszka@siemens.com \
    --cc=markmc@redhat.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.