From: Hannes Frederic Sowa <hannes@redhat•com>
To: Cong Wang <cwang@twopensource•com>
Cc: Mahesh Bandewar <maheshb@google•com>,
netdev <netdev@vger•kernel.org>,
Eric Dumazet <edumazet@google•com>,
Maciej Zenczykowski <maze@google•com>,
Laurent Chavey <chavey@google•com>,
Tim Hockin <thockin@google•com>,
David Miller <davem@davemloft•net>,
Brandon Philips <brandon.philips@coreos•com>,
Pavel Emelianov <xemul@parallels•com>
Subject: Re: [PATCH net-next 1/1] ipvlan: Initial check-in of the IPVLAN driver.
Date: Wed, 12 Nov 2014 00:22:40 +0100 [thread overview]
Message-ID: <1415748160.2292.8.camel@localhost> (raw)
In-Reply-To: <CAHA+R7OZxCLFYetGHONWkL7uzGur=xSc=ASBT4i5EEeS2Xzwog@mail.gmail.com>
On Di, 2014-11-11 at 15:12 -0800, Cong Wang wrote:
> On Tue, Nov 11, 2014 at 2:29 PM, Mahesh Bandewar <maheshb@google•com> wrote:
> > This driver is very similar to the macvlan driver except that it
> > uses L3 on the frame to determine the logical interface while
> > functioning as packet dispatcher. It inherits L2 of the master
> > device hence the packets on wire will have the same L2 for all
> > the packets originating from all virtual devices off of the same
> > master device.
>
> Why do we need this from the beginning?
> IOW, what problem does this solve while macvlan doesn't?
I think it is good to reduce the number of mac addresses before a NIC
switches into promisc mode.
Bye,
Hannes
next prev parent reply other threads:[~2014-11-11 23:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 22:29 [PATCH net-next 1/1] ipvlan: Initial check-in of the IPVLAN driver Mahesh Bandewar
2014-11-11 23:12 ` Cong Wang
2014-11-11 23:19 ` David Miller
2014-11-12 0:37 ` Cong Wang
2014-11-11 23:22 ` Hannes Frederic Sowa [this message]
2014-11-12 0:39 ` Cong Wang
2014-11-12 2:29 ` Eric Dumazet
2014-11-12 2:46 ` Mahesh Bandewar
2014-11-11 23:28 ` Eric Dumazet
2014-11-12 23:36 ` Mahesh Bandewar
2014-11-12 16:11 ` Pavel Emelyanov
2014-11-12 23:56 ` Mahesh Bandewar
2014-11-13 11:07 ` Pavel Emelyanov
2014-11-13 16:50 ` Mahesh Bandewar
2014-11-13 15:57 ` Pavel Emelyanov
-- strict thread matches above, loose matches on Subject: below --
2014-11-13 23:25 Alexei Starovoitov
2014-11-14 5:47 ` Mahesh Bandewar
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=1415748160.2292.8.camel@localhost \
--to=hannes@redhat$(echo .)com \
--cc=brandon.philips@coreos$(echo .)com \
--cc=chavey@google$(echo .)com \
--cc=cwang@twopensource$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=maheshb@google$(echo .)com \
--cc=maze@google$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=thockin@google$(echo .)com \
--cc=xemul@parallels$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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