All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark McLoughlin <markmc@redhat.com>
To: "Fischer, Anna" <anna.fischer@hp.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Network throughput limits for local VM <-> VM communication
Date: Tue, 09 Jun 2009 14:39:40 +0100	[thread overview]
Message-ID: <1244554780.11883.21.camel@blaa> (raw)
In-Reply-To: <0199E0D51A61344794750DC57738F58E67D2398F9E@GVW1118EXC.americas.hpqcorp.net>

On Tue, 2009-06-09 at 11:06 +0000, Fischer, Anna wrote:

> I am testing network throughput between two guests residing on the
> same physical machine. I use a bridge to pass packets between those
> guests and the virtio NIC model. I am wondering why the throughput
> only goes up to about 970Mbps. Should we not be able to achieve much
> higher throughput if the packets do not actually go out on the
> physical wire? What are the limitations for throughput performance
> under KVM/virtio? I can see that by default the interfaces (the tap
> devices) have TX queue length set to 500, and I wonder if increasing
> this would make any difference? Also, are there other things I would
> need to consider to achieve higher throughput numbers for local guest
> <-> guest communication? The CPU is not maxed out at all, and shows as
> being idle for most of the time while the throughput does not increase
> any more.
> 
> I run KVM under standard Fedora Core 10 with a Linux kernel 2.6.27.

The first thing to check is that GSO is enabled - you can check with
"ethtool -k eth0" in the guests.

Are you starting qemu from the command line or e.g. using libvirt? The
libvirt version in F-10 didn't know how to enable IFF_VNET_HDR on the
tapfd before passing it to qemu.

Really, I'd suggest updating to F-11 before digging further - you'll
have qemu-kvm-0.10.5, linux-2.6.29.4 and libvirt-0.6.2.

Cheers,
Mark.


  reply	other threads:[~2009-06-09 13:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 11:06 Network throughput limits for local VM <-> VM communication Fischer, Anna
2009-06-09 13:39 ` Mark McLoughlin [this message]
2009-06-09 13:55   ` Fischer, Anna
2009-06-10 13:29     ` Arnd Bergmann
2009-06-10 13:57       ` Fischer, Anna
2009-06-11  7:49         ` Arnd Bergmann
2009-06-11  8:01           ` Fischer, Anna
2009-06-11  8:17             ` Avi Kivity
2009-06-11  8:46               ` Fischer, Anna
2009-06-11  8:50                 ` Avi Kivity
2009-06-17  7:36                   ` Fischer, Anna
2009-06-17  7:50                     ` Avi Kivity
2009-06-17  8:12                       ` Fischer, Anna
2009-06-17 12:22                         ` Avi Kivity
2009-06-17 15:41                           ` Fischer, Anna
2009-06-18  8:37                             ` Avi Kivity

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=1244554780.11883.21.camel@blaa \
    --to=markmc@redhat.com \
    --cc=anna.fischer@hp.com \
    --cc=kvm@vger.kernel.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.