| Message ID | 20210416155535.1694714-1-idosch@idosch.org (mailing list archive) |
|---|---|
| Headers | show |
| Series | nexthop: Support large scale nexthop flushing | expand |
Hello: This series was applied to netdev/net-next.git (refs/heads/master): On Fri, 16 Apr 2021 18:55:33 +0300 you wrote: > From: Ido Schimmel <idosch@nvidia.com> > > Patch #1 fixes a day-one bug in the nexthop code and allows "ip nexthop > flush" to work correctly with large number of nexthops that do not fit > in a single-part dump. > > Patch #2 adds a test case. > > [...] Here is the summary with links: - [net-next,1/2] nexthop: Restart nexthop dump based on last dumped nexthop identifier https://git.kernel.org/netdev/net-next/c/9e46fb656fdb - [net-next,2/2] selftests: fib_nexthops: Test large scale nexthop flushing https://git.kernel.org/netdev/net-next/c/bf5eb67dc80a You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
From: Ido Schimmel <idosch@nvidia.com> Patch #1 fixes a day-one bug in the nexthop code and allows "ip nexthop flush" to work correctly with large number of nexthops that do not fit in a single-part dump. Patch #2 adds a test case. Targeting at net-next since this use case never worked, the flow is pretty obscure and such a large number of nexthops is unlikely to be used in any real-world scenario. Tested with fib_nexthops.sh: Tests passed: 219 Tests failed: 0 Ido Schimmel (2): nexthop: Restart nexthop dump based on last dumped nexthop identifier selftests: fib_nexthops: Test large scale nexthop flushing net/ipv4/nexthop.c | 14 ++++++-------- tools/testing/selftests/net/fib_nexthops.sh | 15 +++++++++++++++ 2 files changed, 21 insertions(+), 8 deletions(-)