On 24/09/17 20:22, Jiri Pirko wrote:
> From: Yotam Gigi <yot...@mellanox.com>
>
> 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 <yot...@mellanox.com>
> Reviewed-by: Ido Schimmel <ido...@mellanox.com>
> Signed-off-by: Jiri Pirko <j...@mellanox.com>
> ---
> include/net/fib_notifier.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/net/fib_notifier.h b/include/net/fib_notifier.h
> index 669b971..54cd6b8 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 {
>
Reviewed-by: Nikolay Aleksandrov <niko...@cumulusnetworks.com>
