netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Ido Schimmel <idosch@mellanox.com>
Cc: netdev@vger.kernel.org, jiri@mellanox.com, dsahern@gmail.com,
	mlxsw@mellanox.com
Subject: Re: [PATCH iproute2 net-next] iproute: Display offload indication per-nexthop
Date: Thu, 3 Aug 2017 09:16:15 -0700	[thread overview]
Message-ID: <20170803091615.3ef64de1@xeon-e3> (raw)
In-Reply-To: <20170803061355.6474-1-idosch@mellanox.com>

On Thu,  3 Aug 2017 09:13:55 +0300
Ido Schimmel <idosch@mellanox.com> 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(+)
> 
> diff --git a/ip/iproute.c b/ip/iproute.c
> index cb695ad..39af38c 100644
> --- a/ip/iproute.c
> +++ b/ip/iproute.c
> @@ -696,6 +696,8 @@ int print_route(const struct sockaddr_nl *who, struct nlmsghdr *n, void *arg)
>  				fprintf(fp, "onlink ");
>  			if (nh->rtnh_flags & RTNH_F_PERVASIVE)
>  				fprintf(fp, "pervasive ");
> +			if (nh->rtnh_flags & RTNH_F_OFFLOAD)
> +				fprintf(fp, "offload ");
>  			if (nh->rtnh_flags & RTNH_F_LINKDOWN)
>  				fprintf(fp, "linkdown ");
>  			len -= NLMSG_ALIGN(nh->rtnh_len);

Yet another set of flags that needs to be table driven..

      parent reply	other threads:[~2017-08-03 16:16 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
2017-08-03 16:16 ` Stephen Hemminger [this message]

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=20170803091615.3ef64de1@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=dsahern@gmail.com \
    --cc=idosch@mellanox.com \
    --cc=jiri@mellanox.com \
    --cc=mlxsw@mellanox.com \
    --cc=netdev@vger.kernel.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).