[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <160312349392.7917.6673239142315191801.stgit@toke.dk>
Date: Mon, 19 Oct 2020 18:04:53 +0200
From: Toke Høiland-Jørgensen <toke@...hat.com>
To: Daniel Borkmann <daniel@...earbox.net>
Cc: David Ahern <dsahern@...nel.org>, netdev@...r.kernel.org,
bpf@...r.kernel.org
Subject: [PATCH bpf 0/2] bpf: Rework bpf_redirect_neigh() to allow supplying
nexthop from caller
Based on previous discussion[0], we determined that it would be beneficial to
rework bpf_redirect_neigh() so the caller can supply the nexthop information
(e.g., from a previous call to bpf_fib_lookup()). This way, the two helpers can
be combined without incurring a second FIB lookup to find the nexthop, and
bpf_fib_lookup() becomes usable even if no nexthop entry currently exists.
This patch (and accompanying selftest update) accomplishes this by way of an
optional paramter to bpf_redirect_neigh(). This series is against the -bpf tree,
since we need to change this call signature before it becomes API.
[0] https://lore.kernel.org/bpf/393e17fc-d187-3a8d-2f0d-a627c7c63fca@iogearbox.net/
Changelog:
v1:
- Rebase on -bpf tree
- Fix compilation with INET/INET6 disabled (kbot)
- Keep v4/v6 signatures similar, use internal flag (Daniel)
- Use a separate selftest BPF program instead of modifying existing one (Daniel)
- Fix a few style nits (David Ahern)
---
Toke Høiland-Jørgensen (2):
bpf_redirect_neigh: Support supplying the nexthop as a helper parameter
selftests: Update test_tc_redirect.sh to use the modified bpf_redirect_neigh()
.../selftests/bpf/progs/test_tc_neigh.c | 5 +-
.../selftests/bpf/progs/test_tc_neigh_fib.c | 142 ++++++++++++++++++
.../testing/selftests/bpf/test_tc_redirect.sh | 27 +++-
3 files changed, 169 insertions(+), 5 deletions(-)
create mode 100644 tools/testing/selftests/bpf/progs/test_tc_neigh_fib.c
Powered by blists - more mailing lists