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:50:46 +0300 [thread overview]
Message-ID: <4A30C566.7040109@redhat.com> (raw)
In-Reply-To: <0199E0D51A61344794750DC57738F58E67D2399972@GVW1118EXC.americas.hpqcorp.net>
Fischer, Anna wrote:
> Not sure I understand. As far as I can see the packets are replicated on the tun/tap interface before they actually enter the bridge. So this is not about the bridge learning MAC addresses and flooding frames to unknown destinations. So I think this is different.
>
Okay.
You said:
> 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.
Well, it shouldn't. The tun interface should pass the packets to just
one tap interface.
Can you post the qemu command line you're using? There's a gotcha there
that can result in what you're seeing.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-11 8:50 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
2009-06-11 8:46 ` Fischer, Anna
2009-06-11 8:50 ` Avi Kivity [this message]
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=4A30C566.7040109@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 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).