diff options
| author | Ido Schimmel <idosch@nvidia.com> | 2021-03-24 22:14:23 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2021-03-24 16:34:58 -0700 |
| commit | 861584724c44e63bfb684090c70ade660dae6c69 (patch) | |
| tree | 69c1d2967183e1e167480054ba9825a44fab6fbd /scripts/bpf_doc.py | |
| parent | 03490a8239156933366f5595250fe3dc5d0e18aa (diff) | |
selftests: mlxsw: Test unresolved neigh trap with resilient nexthop groups
The number of nexthop buckets in a resilient nexthop group never
changes, so when the gateway address of a nexthop cannot be resolved,
the nexthop buckets are programmed to trap packets to the CPU in order
to trigger resolution. For example:
# ip nexthop add id 1 via 198.51.100.1 dev swp3
# ip nexthop add id 10 group 1 type resilient buckets 32
# ip nexthop bucket get id 10 index 0
id 10 index 0 idle_time 1.44 nhid 1 trap
Where 198.51.100.1 is a made-up IP.
Test that in this case packets are indeed trapped to the CPU via the
unresolved neigh trap.
Signed-off-by: Ido Schimmel <idosch@nvidia.com>
Reviewed-by: Petr Machata <petrm@nvidia.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'scripts/bpf_doc.py')
0 files changed, 0 insertions, 0 deletions