Thread (19 messages) flat view 19 messages, 6 authors, 2017-02-11

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

From: Stephen Hemminger <stephen@networkplumber.org>
Date: 2017-02-02 04:04:26

On Wed, 01 Feb 2017 20:02:35 -0800
Roopa Prabhu [off-list ref] wrote:
On 2/1/17, 5:59 PM, David Ahern wrote:
quoted
On 2/1/17 6:23 PM, Alexei Starovoitov wrote:  
quoted
On Tue, Jan 31, 2017 at 10:59:50PM -0800, Roopa Prabhu wrote:  
quoted
                    
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help