From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hannes Frederic Sowa Subject: Re: [PATCH net-next 1/1] ipvlan: Initial check-in of the IPVLAN driver. Date: Wed, 12 Nov 2014 00:22:40 +0100 Message-ID: <1415748160.2292.8.camel@localhost> References: <1415744984-25802-1-git-send-email-maheshb@google.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Mahesh Bandewar , netdev , Eric Dumazet , Maciej Zenczykowski , Laurent Chavey , Tim Hockin , David Miller , Brandon Philips , Pavel Emelianov To: Cong Wang Return-path: Received: from mx1.redhat.com ([209.132.183.28]:50041 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752493AbaKKXWw (ORCPT ); Tue, 11 Nov 2014 18:22:52 -0500 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Di, 2014-11-11 at 15:12 -0800, Cong Wang wrote: > On Tue, Nov 11, 2014 at 2:29 PM, Mahesh Bandewar 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