[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <36964869-b0d4-1b03-ca28-654ac3727283@gmail.com>
Date: Tue, 15 Aug 2017 08:18:36 -0600
From: David Ahern <dsahern@...il.com>
To: Jiri Pirko <jiri@...nulli.us>, netdev@...r.kernel.org
Cc: davem@...emloft.net, idosch@...lanox.com, mlxsw@...lanox.com,
roopa@...ulusnetworks.com, nikolay@...ulusnetworks.com,
hannes@...essinduktion.org, yoshfuji@...ux-ipv6.org,
kuznet@....inr.ac.ru
Subject: Re: [patch net-next] ipv6: fib: Provide offload indication using
nexthop flags
On 8/15/17 1:09 AM, Jiri Pirko wrote:
> From: Ido Schimmel <idosch@...lanox.com>
>
> IPv6 routes currently lack nexthop flags as in IPv4. This has several
> implications.
>
> In the forwarding path, it requires us to check the carrier state of the
> nexthop device and potentially ignore a linkdown route, instead of
> checking for RTNH_F_LINKDOWN.
>
> It also requires capable drivers to use the user facing IPv6-specific
> route flags to provide offload indication, instead of using the nexthop
> flags as in IPv4.
>
> Add nexthop flags to IPv6 routes in the 40 bytes hole and use it to
> provide offload indication instead of the RTF_OFFLOAD flag, which is
> removed while it's still not part of any official kernel release.
>
> In the near future we would like to use the field for the
> RTNH_F_{LINKDOWN,DEAD} flags, but this change is more involved and might
> not be ready in time for the current cycle.
>
> Signed-off-by: Ido Schimmel <idosch@...lanox.com>
> Signed-off-by: Jiri Pirko <jiri@...lanox.com>
> ---
> drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c | 8 ++++----
> include/net/ip6_fib.h | 2 ++
> include/uapi/linux/ipv6_route.h | 1 -
> net/ipv6/route.c | 7 +------
> 4 files changed, 7 insertions(+), 11 deletions(-)
LGTM.
Acked-by: David Ahern <dsahern@...il.com>
Powered by blists - more mailing lists