From: David Ahern <dsahern@gmail.com>
To: Ido Schimmel <idosch@mellanox.com>, netdev@vger.kernel.org
Cc: stephen@networkplumber.org, jiri@mellanox.com, mlxsw@mellanox.com
Subject: Re: [PATCH iproute2 net-next] iproute: Display offload indication per-nexthop
Date: Thu, 3 Aug 2017 08:26:29 -0600 [thread overview]
Message-ID: <86fc8356-f5f7-2615-eb12-7b49a2b195d6@gmail.com> (raw)
In-Reply-To: <20170803061355.6474-1-idosch@mellanox.com>
On 8/3/17 12:13 AM, Ido Schimmel wrote:
> Since kernel commit 475abbf1ef67 ("ipv4: fib: Set offload indication
> according to nexthop flags") offload indication is reported on a
> per-nexthop basis.
>
> Adjust iproute2 to display it.
>
> Signed-off-by: Ido Schimmel <idosch@mellanox.com>
> Reviewed-by: Jiri Pirko <jiri@mellanox.com>
> ---
> ip/iproute.c | 2 ++
> 1 file changed, 2 insertions(+)
>
Acked-by: David Ahern <dsahern@gmail.com>
next prev parent reply other threads:[~2017-08-03 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 6:13 [PATCH iproute2 net-next] iproute: Display offload indication per-nexthop Ido Schimmel
2017-08-03 14:26 ` David Ahern [this message]
2017-08-03 16:16 ` Stephen Hemminger
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=86fc8356-f5f7-2615-eb12-7b49a2b195d6@gmail.com \
--to=dsahern@gmail.com \
--cc=idosch@mellanox.com \
--cc=jiri@mellanox.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).