diff options
author | David S. Miller <davem@davemloft.net> | 2017-08-02 17:00:24 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-08-02 17:00:24 -0700 |
commit | 5a4d148f0d781129137c790936e3ced767987daf (patch) | |
tree | 15457bcac551eabf7c125ddf8883c13490d1ed31 /net/x25 | |
parent | 9820355f6934ba7ba6218abd44df7ee12b65f029 (diff) | |
parent | 2202e35d47fff379fc744e6bd3c111b018cc77df (diff) |
Merge branch 'per-nexthop-offload'
Jiri Pirko says:
====================
ipv4: fib: Provide per-nexthop offload indication
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.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/x25')
0 files changed, 0 insertions, 0 deletions