From: Or Gerlitz <ogerlitz@Voltaire.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Mark McLoughlin <markmc@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
netdev@vger.kernel.org, Dor Laor <dlaor@redhat.com>,
qemu-devel@nongnu.org, Jan Kiszka <jan.kiszka@web.de>
Subject: Re: [Qemu-devel] [PATCH] net: add raw backend - some performance measurements
Date: Tue, 21 Jul 2009 16:41:38 +0300 [thread overview]
Message-ID: <4A65C592.4060103@Voltaire.com> (raw)
In-Reply-To: <20090721121420.GA19236@gondor.apana.org.au>
Herbert Xu wrote:
> On Tue, Jul 21, 2009 at 03:01:42PM +0300, Michael S. Tsirkin wrote:
>> the thing to check then would be that some kind of misconfiguration
>> does not cause the bridge to flood your packets to multiple interfaces.
> Right, we should make sure that the interfaces are not in promiscous mode
Michael, Herbert,
First, I don't see how flooding can happen in my setup, I have only two interfaces on
the bridge (see below), a tap and a NIC (vlan) and the bridge will never attempt to forward
a packet through the port it was received. Second, the bridge always set all interfaces
attached to it to be in promiscous mode, see the call to dev_set_promiscuity() from br_add_if()
but this doesn't mean it applied flooding, it does mac learning...
Or.
# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.0030485f9977 no eth1.4009
tap0
The VM mac is de:ab:be:01:01:09 and the remote node mac is 00:30:48:65:a6:2b, you
can see that these two macs were learned by the bridge and hence no flooding is expected.
# brctl showmacs br0
port no mac addr is local? ageing timer
1 00:30:48:5f:99:77 yes 0.00
1 00:30:48:65:a6:2b no 12.50
2 06:f5:76:64:a0:d4 yes 0.00
2 de:ab:be:01:01:09 no 0.00
next prev parent reply other threads:[~2009-07-21 13:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 15:46 [Qemu-devel] [PATCH] net: add raw backend Or Gerlitz
2009-07-01 16:21 ` Jamie Lokier
2009-07-02 12:25 ` Or Gerlitz
2009-07-03 2:39 ` Jamie Lokier
2009-07-07 13:33 ` Or Gerlitz
2009-07-07 14:57 ` Jamie Lokier
2009-07-08 14:45 ` Or Gerlitz
2009-07-14 13:54 ` Or Gerlitz
2009-07-15 20:38 ` Jamie Lokier
2009-07-15 21:06 ` Jan Kiszka
2009-07-15 21:52 ` Jamie Lokier
2009-07-16 8:29 ` Or Gerlitz
2009-07-20 14:13 ` [Qemu-devel] [PATCH] net: add raw backend - some performance measurements Or Gerlitz
2009-07-20 15:53 ` Herbert Xu
2009-07-20 18:20 ` Michael S. Tsirkin
2009-07-21 1:46 ` Herbert Xu
2009-07-21 7:03 ` Or Gerlitz
2009-07-21 7:25 ` Herbert Xu
2009-07-21 10:17 ` Or Gerlitz
2009-07-21 10:27 ` Michael S. Tsirkin
2009-07-21 11:05 ` Or Gerlitz
2009-07-21 12:01 ` Michael S. Tsirkin
2009-07-21 12:14 ` Herbert Xu
2009-07-21 13:41 ` Or Gerlitz [this message]
[not found] ` <5b31733c0907011250i7afcdbcdnb844290de4ad64f2@mail.gmail.com>
2009-07-02 12:08 ` [Qemu-devel] [PATCH] net: add raw backend Or Gerlitz
2009-07-02 15:43 ` Michael S. Tsirkin
2009-07-07 14:45 ` Or Gerlitz
2009-07-07 14:49 ` Michael S. Tsirkin
2009-07-08 14:46 ` Or Gerlitz
2009-07-08 15:06 ` Or Gerlitz
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=4A65C592.4060103@Voltaire.com \
--to=ogerlitz@voltaire.com \
--cc=dlaor@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=jan.kiszka@web.de \
--cc=markmc@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--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).