net-next.git - net-next plumbings

summary refs log tree commit diff

path: root/net/qrtr/qrtr.c

diff options

Diffstat (limited to 'net/qrtr/qrtr.c')

0 files changed, 0 insertions, 0 deletions

e.g., no carrier) and the device should do the same. Upon the reception of NH_{ADD,DEL} events, add or remove a nexthop from the device's adjacency table and refresh all the routes using the nexthop group. If all the nexthops of a multipath route are invalid, then any packet hitting the route would be trapped to the CPU for forwarding. If all the nexthops are DEAD, then the kernel would remove the route entirely. On the other hand, if all the nexthops are merely LINKDOWN, then the kernel would keep the route and forward any incoming packet using a different route. While the last case might sound like a problem, it's expected that a routing daemon running in user space would remove such a route from the FIB as it's dumped with the DEAD flag set. Signed-off-by: Ido Schimmel <idosch@mellanox.com> Signed-off-by: Jiri Pirko <jiri@mellanox.com> Signed-off-by: David S. Miller <davem@davemloft.net>

-rw-r--r--

drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c

59

1 files changed, 57 insertions, 2 deletions