diff options
| author | Yotam Gigi <yotamg@mellanox.com> | 2017-09-27 09:23:11 +0300 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2017-09-27 21:33:27 +0300 |
| commit | 85e482285bbbd508483cbe08de69c8fe00cdbbfe (patch) | |
| tree | 267b0afc209f44e57aa51e6fb602616e0d5ccd98 /include/net/fib_notifier.h | |
| parent | 1ca94d7936a409ff263b6e0225fefea8956f4291 (diff) | |
| download | linux-85e482285bbbd508483cbe08de69c8fe00cdbbfe.tar.xz | |
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 'include/net/fib_notifier.h')
| -rw-r--r-- | include/net/fib_notifier.h | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/include/net/fib_notifier.h b/include/net/fib_notifier.h index 669b9716dc7a..54cd6b839d2f 100644 --- a/include/net/fib_notifier.h +++ b/include/net/fib_notifier.h @@ -20,6 +20,8 @@ enum fib_event_type { FIB_EVENT_RULE_DEL, FIB_EVENT_NH_ADD, FIB_EVENT_NH_DEL, + FIB_EVENT_VIF_ADD, + FIB_EVENT_VIF_DEL, }; struct fib_notifier_ops { |