From: Stephen Hemminger <shemminger@linux-foundation.org>
To: "Paul Congdon (UC Davis)" <ptcongdon@ucdavis.edu>
Cc: arnd@arndb.de, anna.fischer@hp.com, netdev@vger.kernel.org,
bridge@lists.linux-foundation.org, davem@davemloft.net,
adobriyan@gmail.com, virtualization@lists.linux-foundation.org
Subject: Re: [Bridge] [evb] RE: [PATCH][RFC] net/bridge: add basic VEPA support
Date: Fri, 7 Aug 2009 14:36:52 -0700 [thread overview]
Message-ID: <20090807143652.1659ac57@nehalam> (raw)
In-Reply-To: <000001ca17a3$03f841f0$0be8c5d0$@edu>
On Fri, 7 Aug 2009 14:06:58 -0700
"Paul Congdon \(UC Davis\)" <ptcongdon@ucdavis.edu> wrote:
> 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.
I have a patch that forwards all multicast packets, and another that does
proper forwarding. It should have worked that way in original macvlan, the
current behavior is really a bug.
--
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: "Paul Congdon \(UC Davis\)" <ptcongdon@ucdavis.edu>
Cc: <anna.fischer@hp.com>, <bridge@lists.linux-foundation.org>,
<netdev@vger.kernel.org>,
<virtualization@lists.linux-foundation.org>,
<davem@davemloft.net>, <kaber@trash.net>, <adobriyan@gmail.com>,
<arnd@arndb.de>
Subject: Re: [evb] RE: [PATCH][RFC] net/bridge: add basic VEPA support
Date: Fri, 7 Aug 2009 14:36:52 -0700 [thread overview]
Message-ID: <20090807143652.1659ac57@nehalam> (raw)
In-Reply-To: <000001ca17a3$03f841f0$0be8c5d0$@edu>
On Fri, 7 Aug 2009 14:06:58 -0700
"Paul Congdon \(UC Davis\)" <ptcongdon@ucdavis.edu> wrote:
> 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.
I have a patch that forwards all multicast packets, and another that does
proper forwarding. It should have worked that way in original macvlan, the
current behavior is really a bug.
--
next prev parent reply other threads:[~2009-08-07 21:36 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 20:35 [Bridge] [evb] RE: [PATCH][RFC] net/bridge: add basic VEPA support Yaron Haviv
2009-08-07 20:35 ` Yaron Haviv
2009-08-07 20:35 ` Yaron Haviv
2009-08-07 21:00 ` [Bridge] " Fischer, Anna
2009-08-07 21:00 ` Fischer, Anna
2009-08-08 9:22 ` [Bridge] " Arnd Bergmann
2009-08-08 9:22 ` Arnd Bergmann
2009-08-08 9:22 ` Arnd Bergmann
2009-08-07 21:00 ` Fischer, Anna
2009-08-07 21:06 ` [Bridge] " Paul Congdon (UC Davis)
2009-08-07 21:06 ` Paul Congdon (UC Davis)
2009-08-07 21:36 ` Stephen Hemminger [this message]
2009-08-07 21:36 ` Stephen Hemminger
2009-08-09 11:19 ` [Bridge] " Or Gerlitz
2009-08-09 11:19 ` Or Gerlitz
2009-08-10 15:20 ` Stephen Hemminger
2009-08-10 15:20 ` [Bridge] " Stephen Hemminger
2009-08-10 15:20 ` Stephen Hemminger
2009-08-10 15:28 ` [Bridge] " Arnd Bergmann
2009-08-10 15:28 ` Arnd Bergmann
2009-08-10 16:32 ` [Bridge] " Fischer, Anna
2009-08-10 16:32 ` Fischer, Anna
2009-08-10 16:51 ` [Bridge] " Stephen Hemminger
2009-08-10 16:51 ` Stephen Hemminger
2009-08-10 19:18 ` Arnd Bergmann
2009-08-10 19:18 ` [Bridge] " Arnd Bergmann
2009-08-10 19:18 ` Arnd Bergmann
2009-08-10 16:51 ` Stephen Hemminger
2009-08-10 16:32 ` Fischer, Anna
2009-08-10 15:28 ` Arnd Bergmann
2009-08-27 12:35 ` Or Gerlitz
2009-08-27 12:35 ` [Bridge] " Or Gerlitz
2009-08-27 12:35 ` Or Gerlitz
2009-08-09 11:19 ` Or Gerlitz
2009-08-07 21:36 ` Stephen Hemminger
2009-08-07 21:06 ` Paul Congdon (UC Davis)
[not found] ` <0199E0D51A61344794750DC57738F58E6D6A6CD803__29862.6656564467$1249679159$gmane$org@GVW1118EXC.americas.hpqcorp.net>
2009-08-08 8:50 ` [Bridge] " Benny Amorsen
2009-08-08 8:50 ` Benny Amorsen
2009-08-08 9:44 ` Arnd Bergmann
2009-08-08 9:44 ` [Bridge] " Arnd Bergmann
2009-08-08 9:44 ` Arnd Bergmann
2009-08-08 8:50 ` Benny Amorsen
-- strict thread matches above, loose matches on Subject: below --
2009-06-15 17:33 [Bridge] " Fischer, Anna
2009-08-07 4:00 ` Stephen Hemminger
2009-08-07 11:29 ` Arnd Bergmann
2009-08-07 19:44 ` [Bridge] [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=20090807143652.1659ac57@nehalam \
--to=shemminger@linux-foundation.org \
--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=ptcongdon@ucdavis.edu \
--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 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.