summaryrefslogtreecommitdiffstats
path: root/net/ipv4
diff options
context:
space:
mode:
authorYotam Gigi2017-09-27 08:23:11 +0200
committerDavid S. Miller2017-09-27 20:33:27 +0200
commit85e482285bbbd508483cbe08de69c8fe00cdbbfe (patch)
tree267b0afc209f44e57aa51e6fb602616e0d5ccd98 /net/ipv4
parentMerge branch 'nfp-flower-vxlan-tunnel-offload' (diff)
downloadkernel-qcow2-linux-85e482285bbbd508483cbe08de69c8fe00cdbbfe.tar.gz
kernel-qcow2-linux-85e482285bbbd508483cbe08de69c8fe00cdbbfe.tar.xz
kernel-qcow2-linux-85e482285bbbd508483cbe08de69c8fe00cdbbfe.zip
fib: notifier: Add VIF add and delete event types
In order for an interface to forward packets according to the kernel multicast routing table, it must be configured with a VIF index according to the mroute user API. The VIF index is then used to refer to that interface in the mroute user API, for example, to set the iif and oifs of an MFC entry. In order to allow drivers to be aware and offload multicast routes, they have to be aware of the VIF add and delete notifications. Due to the fact that a specific VIF can be deleted and re-added pointing to another netdevice, and the MFC routes that point to it will forward the matching packets to the new netdevice, a driver willing to offload MFC cache entries must be aware of the VIF add and delete events in addition to MFC routes notifications. Signed-off-by: Yotam Gigi <yotamg@mellanox.com> Reviewed-by: Ido Schimmel <idosch@mellanox.com> Signed-off-by: Jiri Pirko <jiri@mellanox.com> Reviewed-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv4')
0 files changed, 0 insertions, 0 deletions