[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8f79898c-3708-5001-54f9-e882c05075a8@cumulusnetworks.com>
Date: Wed, 15 Mar 2017 09:16:47 -0600
From: David Ahern <dsa@...ulusnetworks.com>
To: Jiri Pirko <jiri@...nulli.us>, netdev@...r.kernel.org
Cc: davem@...emloft.net, idosch@...lanox.com, mlxsw@...lanox.com,
shm@...ulusnetworks.com, kuznet@....inr.ac.ru, jmorris@...ei.org,
yoshfuji@...ux-ipv6.org, kaber@...sh.net, lorenzo@...gle.com,
mateusz.bajorski@...ia.com
Subject: Re: [patch net-next v2 2/9] ipv4: fib_rules: Add notifier info to FIB
rules notifications
On 3/15/17 5:05 AM, Jiri Pirko wrote:
> From: Ido Schimmel <idosch@...lanox.com>
>
> Whenever a FIB rule is added or removed, a notification is sent in the
> FIB notification chain. However, listeners don't have a way to tell
> which rule was added or removed.
>
> This is problematic as we would like to give listeners the ability to
> decide which action to execute based on the notified rule. Specifically,
> offloading drivers should be able to determine if they support the
> reflection of the notified FIB rule and flush their LPM tables in case
> they don't.
>
> Do that by adding a notifier info to these notifications and embed the
> common FIB rule struct in it.
>
> Signed-off-by: Ido Schimmel <idosch@...lanox.com>
> Signed-off-by: Jiri Pirko <jiri@...lanox.com>
> ---
> include/net/ip_fib.h | 5 +++++
> net/ipv4/fib_rules.c | 13 ++++++++-----
> 2 files changed, 13 insertions(+), 5 deletions(-)
Acked-by: David Ahern <dsa@...ulusnetworks.com>
Powered by blists - more mailing lists