Subject: Re: [PATCH net-next v2 0/5] bridge: per vlan dst_metadata support

From: Stephen Hemminger <[email-masked]>
Date: Wed, 1 Feb 2017 20:04:18 -0800

On Wed, 01 Feb 2017 20:02:35 -0800
Roopa Prabhu <[email-masked]> wrote:

> On 2/1/17, 5:59 PM, David Ahern wrote:
> > On 2/1/17 6:23 PM, Alexei Starovoitov wrote:  
> >> On Tue, Jan 31, 2017 at 10:59:50PM -0800, Roopa Prabhu wrote:  
> >>>                     
> >>> This provides the required vxlan bridging function but poses a
> >>> scalability problem with using a separate vxlan netdev for each vni.  
> >> if I remember correctly this issue was the main reason David Ahern
> >> put netdev on diet. Sounds like no more fun at netconf ;)
> >>  
> > oh, it still needs a diet ...  
>  Even if the netdev went on diet, a netdev per vni for vxlan deployments is just too much overhead.
> 
> 

But the intent was VNI == VLAN tag and there are cases where you need per VNI rules.
Having them all smashed into one netdev seems like a step in the wrong direction.