Re: [RFC PATCH net-next 4/5] bridge: vlan lwt and dst_metadata netlink support

2017-01-23 Thread Roopa Prabhu
On 1/22/17, 4:22 PM, Rosen, Rami wrote: > Hi, Roopa, > > Two minor comments: > > The parameter br is not used in the br_add_vlan_tunnel_info() method, it > should be removed: Thanks Rami. will take care of this in the next version.

RE: [RFC PATCH net-next 4/5] bridge: vlan lwt and dst_metadata netlink support

2017-01-22 Thread Rosen, Rami
Hi, Roopa, Two minor comments: The parameter br is not used in the br_add_vlan_tunnel_info() method, it should be removed: +static int br_add_vlan_tunnel_info(struct net_bridge *br, + struct net_bridge_port *p, int cmd, + u16

Re: [RFC PATCH net-next 4/5] bridge: vlan lwt and dst_metadata netlink support

2017-01-22 Thread Roopa Prabhu
On 1/22/17, 4:05 AM, Nikolay Aleksandrov wrote: > On 21/01/17 06:46, Roopa Prabhu wrote: >> From: Roopa Prabhu >> >> This patch adds support to attach per vlan tunnel info dst >> metadata. This enables bridge driver to map vlan to tunnel_info >> at ingress and egress >>

Re: [RFC PATCH net-next 4/5] bridge: vlan lwt and dst_metadata netlink support

2017-01-22 Thread Nikolay Aleksandrov
On 21/01/17 06:46, Roopa Prabhu wrote: > From: Roopa Prabhu > > This patch adds support to attach per vlan tunnel info dst > metadata. This enables bridge driver to map vlan to tunnel_info > at ingress and egress > > The initial use case is vlan to vni bridging, but

[RFC PATCH net-next 4/5] bridge: vlan lwt and dst_metadata netlink support

2017-01-20 Thread Roopa Prabhu
From: Roopa Prabhu This patch adds support to attach per vlan tunnel info dst metadata. This enables bridge driver to map vlan to tunnel_info at ingress and egress The initial use case is vlan to vni bridging, but the api is generic to extend to any tunnel_info in the