[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <769e0521-3a12-4e52-20ea-8dc3dc5aa60b@gmail.com>
Date: Sun, 7 Jan 2018 10:03:29 -0700
From: David Ahern <dsahern@...il.com>
To: Ido Schimmel <idosch@...lanox.com>, netdev@...r.kernel.org
Cc: davem@...emloft.net, roopa@...ulusnetworks.com,
nicolas.dichtel@...nd.com, weiwan@...gle.com, kafai@...com,
yoshfuji@...ux-ipv6.org, mlxsw@...lanox.com
Subject: Re: [PATCH net-next 11/18] ipv6: Add explicit flush indication to
routes
On 1/7/18 3:45 AM, Ido Schimmel wrote:
> When routes that are a part of a multipath route are evaluated by
> fib6_ifdown() in response to NETDEV_DOWN and NETDEV_UNREGISTER events
> the state of their sibling routes is not considered.
>
> This will change in subsequent patches in order to align IPv6 with
> IPv4's behavior. For example, when the last sibling in a multipath route
> becomes dead, the entire multipath route needs to be removed.
>
> To prevent the tree walker from re-evaluating all the sibling routes
> each time, we can simply evaluate them once - when the first sibling is
> traversed.
>
> If we determine the entire multipath route needs to be removed, then the
> 'should_flush' bit is set in all the siblings, which will cause the
> walker to flush them when it traverses them.
>
> Signed-off-by: Ido Schimmel <idosch@...lanox.com>
> ---
> include/net/ip6_fib.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Acked-by: David Ahern <dsahern@...il.com>
Powered by blists - more mailing lists