diff options
author | David S. Miller <davem@davemloft.net> | 2017-02-08 15:25:19 -0500 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-02-08 15:25:19 -0500 |
commit | d9e1661dab02e62a2ce971cfc2b957ee52f7cdf3 (patch) | |
tree | 0e66a1565e9c0bfd642ac18ecb607d2b074d0253 /tools/build/feature/test-dwarf.c | |
parent | b05d0cfa1932376dc388a0fe67564572a84374a3 (diff) | |
parent | 9665b74562ab95bcf1b0684d599bc6779c433fca (diff) |
Merge branch 'mlxsw-Reflect-nexthop-status-changes'
Jiri Pirko says:
====================
mlxsw: Reflect nexthop status changes
Ido says:
When the kernel forwards IPv4 packets via multipath routes it doesn't
consider nexthops that are dead or linkdown. For example, if the nexthop
netdev is administratively down or doesn't have a carrier.
Devices capable of offloading such multipath routes need to be made
aware of changes in the reflected nexthops' status. Otherwise, the
device might forward packets via non-functional nexthops, resulting in
packet loss. This patchset aims to fix that.
The first 11 patches deal with the necessary restructuring in the
mlxsw driver, so that it's able to correctly add and remove nexthops
from the device's adjacency table.
The 12th patch adds the NH_{ADD,DEL} events to the FIB notification
chain. These notifications are sent whenever the kernel decides to add
or remove a nexthop from the forwarding plane.
Finally, the last three patches add support for these events in the
mlxsw driver, which is currently the only driver capable of offloading
multipath routes.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/build/feature/test-dwarf.c')
0 files changed, 0 insertions, 0 deletions