Re: [PATCH net-next v2 07/12] rtnetlink: add new rtm tunnel api for tunnel id filtering

On Tue, 22 Feb 2022 18:49:03 -0800 Roopa Prabhu wrote:

On 2/22/22 5:26 PM, Jakub Kicinski wrote:

quoted

Why create new RTM_ commands instead of using changelink?

I thought we had to add special commands for bridge because
if the target of the command is not a bridge device but possibly
a bridge port, which could be anything. That's not the case here.

Is it only about the convenience of add/del vs changelink where
we'd potentially have to pass and parse the entire vni list each time?  

yes, exactly. that's the reason. My first internal version used 
changelink and soon realized it was too limiting.

especially notifications. Its too heavy to notify the full vni list 
every-time.

IIRC bridge also went through a similar transition. Now bridge also has 
RTM_*VLAN commands.

Makes sense. I wasn't quite sure if this isn't over-engineering
 - do deployments really use VxLAN devs with many VNIs?

Couldn't think of another way than adding a new msg. Tried to keep the 
name generic for use by potentially other dst/collect metadata devices

Ack, I don't have any better ideas either :)