[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170802.170040.1522837897155424725.davem@davemloft.net>
Date: Wed, 02 Aug 2017 17:00:40 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: jiri@...nulli.us
Cc: netdev@...r.kernel.org, idosch@...lanox.com, mlxsw@...lanox.com,
dsahern@...il.com, roopa@...ulusnetworks.com,
nikolay@...ulusnetworks.com, hannes@...essinduktion.org,
yoshfuji@...ux-ipv6.org, kuznet@....inr.ac.ru
Subject: Re: [patch net-next 0/6] ipv4: fib: Provide per-nexthop offload
indication
From: Jiri Pirko <jiri@...nulli.us>
Date: Wed, 2 Aug 2017 09:56:00 +0200
> From: Jiri Pirko <jiri@...lanox.com>
>
> Ido says:
>
> Offload indication for IPv4 routes is currently set in the FIB info's
> flags. When multipath routes are employed, this can lead to a route being
> marked as offloaded although only one of its nexthops is actually
> offloaded.
>
> Instead, this patchset aims to proivde a higher resolution for the offload
> indication and report it on a per-nexthop basis.
>
> Example output from patched iproute:
>
> $ ip route show 192.168.200.0/24
> 192.168.200.0/24
> nexthop via 192.168.100.2 dev enp3s0np7 weight 1 offload
> nexthop via 192.168.101.3 dev enp3s0np8 weight 1
>
> And once the second gateway is resolved:
>
> $ ip route show 192.168.200.0/24
> 192.168.200.0/24
> nexthop via 192.168.100.2 dev enp3s0np7 weight 1 offload
> nexthop via 192.168.101.3 dev enp3s0np8 weight 1 offload
>
> First patch teaches the kernel to look for the offload indication in the
> nexthop flags. Patches 2-5 adjust current capable drivers to provide
> offload indication on a per-nexthop basis. Last patch removes no longer
> used functions to set offload indication in the FIB info's flags.
Series applied, thanks Jiri.
Powered by blists - more mailing lists