From: "Paul Congdon \(UC Davis\)" <ptcongdon@ucdavis.edu>
To: <shemminger@linux-foundation.org>, <anna.fischer@hp.com>
Cc: arnd@arndb.de, davem@davemloft.net, netdev@vger.kernel.org,
bridge@lists.linux-foundation.org, adobriyan@gmail.com,
virtualization@lists.linux-foundation.org
Subject: Re: [evb] RE: [PATCH][RFC] net/bridge: add basic VEPA support
Date: Fri, 7 Aug 2009 14:06:58 -0700 [thread overview]
Message-ID: <000001ca17a3$03f841f0$0be8c5d0$@edu> (raw)
In-Reply-To: <D2E118A1E7268F449C469EA2F301D92902BC39B2@exil.voltaire.com>
[-- Attachment #1.1: Type: text/plain, Size: 1122 bytes --]
Yaron,
The interface multiplexing can be achieved using macvlan driver or using an SR-IOV capable NIC (the preferred option), macvlan may need to be extended to support VEPA multicast handling, this looks like a rather simple task
Agreed that the hardware solution is preferred so the macvlan implementation doesn’t really matter. If we are talking SR-IOV, then it is direct mapped, regardless of whether there is a VEB or VEPA in the hardware below, so you are bypassing the bridge software code also.
I disagree that adding the multicast handling is simple – while not conceptually hard, it will basically require you to put an address table into the macvlan implementation – if you have that, then why not have just used the one already in the bridge code. If you hook a VEPA up to a non-hairpin mode external bridge, you get the macvlan capability as well.
It also seems to me like the special macvlan interfaces for KVM don’t apply to XEN or a non-virtualized environment? Or more has to be written to make that work? If it is in the bridge code, you get all of this re-use.
[-- Attachment #1.2: Type: text/html, Size: 6831 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Bridge mailing list
Bridge@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/bridge
next prev parent reply other threads:[~2009-08-07 21:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 20:35 [evb] RE: [PATCH][RFC] net/bridge: add basic VEPA support Yaron Haviv
2009-08-07 21:00 ` Fischer, Anna
2009-08-08 9:22 ` Arnd Bergmann
2009-08-07 21:06 ` Paul Congdon (UC Davis) [this message]
2009-08-07 21:36 ` Stephen Hemminger
2009-08-09 11:19 ` Or Gerlitz
2009-08-10 15:20 ` Stephen Hemminger
2009-08-10 15:28 ` Arnd Bergmann
2009-08-10 16:32 ` Fischer, Anna
2009-08-10 16:51 ` Stephen Hemminger
2009-08-10 19:18 ` Arnd Bergmann
2009-08-27 12:35 ` Or Gerlitz
[not found] ` <0199E0D51A61344794750DC57738F58E6D6A6CD803__29862.6656564467$1249679159$gmane$org@GVW1118EXC.americas.hpqcorp.net>
2009-08-08 8:50 ` Benny Amorsen
2009-08-08 9:44 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2009-06-15 17:33 Fischer, Anna
2009-08-07 4:00 ` Stephen Hemminger
2009-08-07 11:29 ` Arnd Bergmann
2009-08-07 19:44 ` [evb] " Paul Congdon (UC Davis)
2009-08-10 15:23 ` Arnd Bergmann
2009-08-10 15:59 ` Fischer, Anna
2009-08-10 16:16 ` Arnd Bergmann
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='000001ca17a3$03f841f0$0be8c5d0$@edu' \
--to=ptcongdon@ucdavis.edu \
--cc=adobriyan@gmail.com \
--cc=anna.fischer@hp.com \
--cc=arnd@arndb.de \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=virtualization@lists.linux-foundation.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).