mbox series

[iproute2,net-next,v2,0/3] support for vxlan vni filtering

Message ID 20220508045340.120653-1-roopa@nvidia.com (mailing list archive)
Headers show
Series support for vxlan vni filtering | expand

Message

Roopa Prabhu May 8, 2022, 4:53 a.m. UTC
This series adds bridge command to manage
recently added vnifilter on a collect metadata
vxlan (external) device. Also includes per vni stats
support.

examples:
$bridge vni add dev vxlan0 vni 400

$bridge vni add dev vxlan0 vni 200 group 239.1.1.101

$bridge vni del dev vxlan0 vni 400

$bridge vni show

$bridge -s vni show

Nikolay Aleksandrov (1):
  bridge: vni: add support for stats dumping

Roopa Prabhu (2):
  bridge: vxlan device vnifilter support
  ip: iplink_vxlan: add support to set vnifiltering flag on vxlan device

v2 : replace matches by strcmp in bridge/vni.c. v2 still uses matches
in iplink_vxlan.c to match the rest of the code

 bridge/Makefile       |   2 +-
 bridge/br_common.h    |   2 +
 bridge/bridge.c       |   1 +
 bridge/monitor.c      |  28 ++-
 bridge/vni.c          | 439 ++++++++++++++++++++++++++++++++++++++++++
 include/libnetlink.h  |   9 +
 ip/iplink_vxlan.c     |  23 ++-
 lib/libnetlink.c      |  20 ++
 man/man8/bridge.8     |  77 +++++++-
 man/man8/ip-link.8.in |   9 +
 10 files changed, 606 insertions(+), 4 deletions(-)
 create mode 100644 bridge/vni.c

Comments

David Ahern May 8, 2022, 3:53 p.m. UTC | #1
On 5/7/22 10:53 PM, Roopa Prabhu wrote:
> This series adds bridge command to manage
> recently added vnifilter on a collect metadata
> vxlan (external) device. Also includes per vni stats
> support.
> 
> examples:
> $bridge vni add dev vxlan0 vni 400
> 
> $bridge vni add dev vxlan0 vni 200 group 239.1.1.101
> 
> $bridge vni del dev vxlan0 vni 400
> 
> $bridge vni show
> 
> $bridge -s vni show
> 
> Nikolay Aleksandrov (1):
>   bridge: vni: add support for stats dumping
> 
> Roopa Prabhu (2):
>   bridge: vxlan device vnifilter support
>   ip: iplink_vxlan: add support to set vnifiltering flag on vxlan device
> 
> v2 : replace matches by strcmp in bridge/vni.c. v2 still uses matches
> in iplink_vxlan.c to match the rest of the code
> 

fixed those as well and applied to iproute2-next. We are not taking any
more uses of matches(), even for legacy commands.
patchwork-bot+netdevbpf@kernel.org May 8, 2022, 4 p.m. UTC | #2
Hello:

This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:

On Sun, 8 May 2022 04:53:37 +0000 you wrote:
> This series adds bridge command to manage
> recently added vnifilter on a collect metadata
> vxlan (external) device. Also includes per vni stats
> support.
> 
> examples:
> $bridge vni add dev vxlan0 vni 400
> 
> [...]

Here is the summary with links:
  - [iproute2,net-next,v2,1/3] bridge: vxlan device vnifilter support
    https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=45cd32f9f7d5
  - [iproute2,net-next,v2,2/3] ip: iplink_vxlan: add support to set vnifiltering flag on vxlan device
    (no matching commit)
  - [iproute2,net-next,v2,3/3] bridge: vni: add support for stats dumping
    https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=40b50f153c52

You are awesome, thank you!
Roopa Prabhu May 8, 2022, 4:13 p.m. UTC | #3
On 5/8/22 08:53, David Ahern wrote:
> On 5/7/22 10:53 PM, Roopa Prabhu wrote:
>> This series adds bridge command to manage
>> recently added vnifilter on a collect metadata
>> vxlan (external) device. Also includes per vni stats
>> support.
>>
>> examples:
>> $bridge vni add dev vxlan0 vni 400
>>
>> $bridge vni add dev vxlan0 vni 200 group 239.1.1.101
>>
>> $bridge vni del dev vxlan0 vni 400
>>
>> $bridge vni show
>>
>> $bridge -s vni show
>>
>> Nikolay Aleksandrov (1):
>>    bridge: vni: add support for stats dumping
>>
>> Roopa Prabhu (2):
>>    bridge: vxlan device vnifilter support
>>    ip: iplink_vxlan: add support to set vnifiltering flag on vxlan device
>>
>> v2 : replace matches by strcmp in bridge/vni.c. v2 still uses matches
>> in iplink_vxlan.c to match the rest of the code
>>
> fixed those as well and applied to iproute2-next. We are not taking any
> more uses of matches(), even for legacy commands.

ok, thank you.