From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 08 May 2009 16:25:55 -0700 (PDT) Message-Id: <20090508.162555.193731410.davem@davemloft.net> From: David Miller In-Reply-To: <20090508161204.134668b9@nehalam> References: <20090508153842.65ce3bed@s6510> <20090508.160008.127530143.davem@davemloft.net> <20090508161204.134668b9@nehalam> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [Bridge] [PATCH] net: introduce a list of device addresses dev_addr_list (v6) List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: shemminger@vyatta.com Cc: ivecera@redhat.com, fubar@us.ibm.com, jpirko@redhat.com, netdev@vger.kernel.org, bridge@lists.linux-foundation.org, linux-kernel@vger.kernel.org, mschmidt@redhat.com, jgarzik@pobox.com, dada1@cosmosbay.com, bonding-devel@lists.sourceforge.net From: Stephen Hemminger Date: Fri, 8 May 2009 16:12:04 -0700 > But the other infrastructure may have same issues (netfilter, etc). > Just seems like it would be either to have multiple network devices > so that upper layers could disambiguate easier. That's quite a heavyweight solution to what is purely an addressing issue, don't you think? We can just revert all of that netdev_ops stuff if you think per-netdev cost doesn't matter :-)