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 1/6] ipv4: fib: Set offload indication according to nexthop flags
Date: Wed, 2 Aug 2017 17:01:30 -0600 [thread overview]
Message-ID: <9232015f-01fc-6131-b64d-3abc68d8f7e5@gmail.com> (raw)
In-Reply-To: <20170802075606.1090-2-jiri@resnulli.us>
On 8/2/17 1:56 AM, Jiri Pirko wrote:
> From: Ido Schimmel <idosch@mellanox.com>
>
> We're going to have capable drivers indicate route offload using the
> nexthop flags, but for non-multipath routes these flags aren't dumped to
> user space.
>
> Instead, set the offload indication in the route message flags.
>
> Signed-off-by: Ido Schimmel <idosch@mellanox.com>
> Signed-off-by: Jiri Pirko <jiri@mellanox.com>
> ---
> net/ipv4/fib_semantics.c | 2 ++
> 1 file changed, 2 insertions(+)
Acked-by: David Ahern <dsahern@gmail.com>
next prev parent reply other threads:[~2017-08-02 23:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 7:56 [patch net-next 0/6] ipv4: fib: Provide per-nexthop offload indication Jiri Pirko
2017-08-02 7:56 ` [patch net-next 1/6] ipv4: fib: Set offload indication according to nexthop flags Jiri Pirko
2017-08-02 23:01 ` David Ahern [this message]
2017-08-02 7:56 ` [patch net-next 2/6] rocker: Provide offload indication using " Jiri Pirko
2017-08-02 7:56 ` [patch net-next 3/6] mlxsw: spectrum_router: " Jiri Pirko
2017-08-02 23:20 ` David Ahern
2017-08-02 7:56 ` [patch net-next 4/6] mlxsw: spectrum_router: Don't check state when refreshing offload indication Jiri Pirko
2017-08-02 23:21 ` David Ahern
2017-08-02 7:56 ` [patch net-next 5/6] mlxsw: spectrum_router: Refresh offload indication upon group refresh Jiri Pirko
2017-08-02 23:20 ` David Ahern
2017-08-02 7:56 ` [patch net-next 6/6] ipv4: fib: Remove unused functions Jiri Pirko
2017-08-02 23:01 ` David Ahern
2017-08-03 0:00 ` [patch net-next 0/6] ipv4: fib: Provide per-nexthop offload indication 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=9232015f-01fc-6131-b64d-3abc68d8f7e5@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).