From: Avi Kivity <avi@redhat.com>
To: "Fischer, Anna" <anna.fischer@hp.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Mark McLoughlin <markmc@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Network throughput limits for local VM <-> VM communication
Date: Thu, 11 Jun 2009 11:17:28 +0300 [thread overview]
Message-ID: <4A30BD98.6040302@redhat.com> (raw)
In-Reply-To: <0199E0D51A61344794750DC57738F58E67D23998F5@GVW1118EXC.americas.hpqcorp.net>
Fischer, Anna wrote:
> I am using two bridges, and yes, in theory, the router should be the only connection between the two guests. However, without VLANs, the tun interface will pass packets to all tap interfaces. It has to, as it doesn't know to which one the packet has to go to. It does not look at packets, it simply copies buffers from userspace to the tap interface in the kernel. The tap interface then eventually drops the packet, if the MAC address does not match its own. So packets will not actually go across both bridges, because the tap interface that should not receive the packet does drop it. However, it does receive the packet and processes it to some extend which causes some overhead. As I was told by someone at KVM/RedHat, this does not happen when using VLANs as then there will be a direct mappi
ng between any tun<->tap device and so no packet replication across multiple tap devices.
>
This only happens if the receiving tap never sends out packets. If the
tap interface does send out packets, the bridge will associate their MAC
address with that interface, and future packets will only be forwarded
there.
Is this your scenario?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-11 8:17 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
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 [this message]
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=4A30BD98.6040302@redhat.com \
--to=avi@redhat.com \
--cc=anna.fischer@hp.com \
--cc=arnd@arndb.de \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.com \
/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.