[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20c7a87f-0278-ef58-417a-e0e63dfe74c7@nvidia.com>
Date: Sun, 8 May 2022 09:13:38 -0700
From: Roopa Prabhu <roopa@...dia.com>
To: David Ahern <dsahern@...il.com>
Cc: netdev@...r.kernel.org, stephen@...workplumber.org,
razor@...ckwall.org
Subject: Re: [PATCH iproute2 net-next v2 0/3] support for vxlan vni filtering
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.
Powered by blists - more mailing lists