Amit Cohen 2dcd22023c vxlan: vxlan_core: Support FDB flushing by destination IP ... Add support for flush VXLAN FDB entries by destination IP. FDB entry is stored as {MAC, SRC_VNI} + remote. The destination IP is an attribute of the remote. For multicast entries, the VXLAN driver stores a linked list of remotes for a given key. In user space, each remote is represented as a separate entry, so when flush is sent with filter of 'destination IP', flush only the match remotes. In case that there are no additional remotes, destroy the entry. For example, the following are stored as one entry with several remotes: $ bridge fdb show dev vx10 00:00:00:00:00:00 dst 192.1.1.3 self permanent 00:00:00:00:00:00 dst 192.1.1.1 self permanent 00:00:00:00:00:00 dst 192.1.1.2 self permanent 00:00:00:00:00:00 dst 192.1.1.1 vni 1000 self permanent When user flush by destination IP x, only the relevant remotes will be flushed: $ bridge fdb flush dev vx10 dst 192.1.1.1 $ bridge fdb show dev vx10 00:00:00:00:00:00 dst 192.1.1.3 self permanent 00:00:00:00:00:00 dst 192.1.1.2 self permanent Signed-off-by: Amit Cohen <amcohen@nvidia.com> Reviewed-by: Ido Schimmel <idosch@nvidia.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2023-10-13 10:00:32 +01:00
..
Makefile	vxlan: mdb: Add MDB control path support	2023-03-17 08:05:49 +00:00
vxlan_core.c	vxlan: vxlan_core: Support FDB flushing by destination IP	2023-10-13 10:00:32 +01:00
vxlan_mdb.c	vxlan: Add MDB data path support	2023-03-17 08:05:50 +00:00
vxlan_multicast.c	vxlan: vni filtering support on collect metadata device	2022-03-01 08:38:02 +00:00
vxlan_private.h	vxlan: Add MDB data path support	2023-03-17 08:05:50 +00:00
vxlan_vnifilter.c	vxlan: vnifilter: Use GFP_KERNEL instead of GFP_ATOMIC	2023-08-22 10:58:45 -07:00