From: David Ahern <dsahern@gmail.com>
To: Jiri Pirko <jiri@resnulli.us>, netdev@vger.kernel.org
Cc: davem@davemloft.net, idosch@mellanox.com, mlxsw@mellanox.com,
roopa@cumulusnetworks.com, nikolay@cumulusnetworks.com,
hannes@stressinduktion.org, yoshfuji@linux-ipv6.org,
kuznet@ms2.inr.ac.ru
Subject: Re: [patch net-next] ipv6: fib: Provide offload indication using nexthop flags
Date: Tue, 15 Aug 2017 08:18:36 -0600 [thread overview]
Message-ID: <36964869-b0d4-1b03-ca28-654ac3727283@gmail.com> (raw)
In-Reply-To: <20170815070949.1363-1-jiri@resnulli.us>
On 8/15/17 1:09 AM, Jiri Pirko wrote:
> From: Ido Schimmel <idosch@mellanox.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@mellanox.com>
> Signed-off-by: Jiri Pirko <jiri@mellanox.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@gmail.com>
next prev parent reply other threads:[~2017-08-15 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 7:09 [patch net-next] ipv6: fib: Provide offload indication using nexthop flags Jiri Pirko
2017-08-15 14:18 ` David Ahern [this message]
2017-08-16 0:05 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=36964869-b0d4-1b03-ca28-654ac3727283@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=idosch@mellanox.com \
--cc=jiri@resnulli.us \
--cc=kuznet@ms2.inr.ac.ru \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.com \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).