From: Daniel Borkmann <daniel@iogearbox.net>
To: ast@kernel.org
Cc: daniel@iogearbox.net, john.fastabend@gmail.com, yhs@fb.com,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: [PATCH bpf-next v3 0/6] Follow-up BPF helper improvements
Date: Fri, 9 Oct 2020 22:42:39 +0200 [thread overview]
Message-ID: <20201009204245.27905-1-daniel@iogearbox.net> (raw)
This series addresses most of the feedback [0] that was to be followed
up from the last series, that is, UAPI helper comment improvements and
getting rid of the ifindex obj file hacks in the selftest by using a
BPF map instead. The __sk_buff data/data_end pointer work, I'm planning
to do in a later round as well as the mem*() BPF improvements we have
in Cilium for libbpf. Next, the series adds two features, i) a helper
called redirect_peer() to improve latency on netns switch, and ii) to
allow map in map with dynamic inner array map sizes. Selftests for each
are added as well. For details, please check individual patches, thanks!
[0] https://lore.kernel.org/bpf/cover.1601477936.git.daniel@iogearbox.net/
v2 -> v3:
- Remove tab that slipped into uapi helper desc (Jakub)
- Rework map in map for array to error from map_gen_lookup (Andrii)
v1 -> v2:
- Fixed selftest comment wrt inner1/inner2 value (Yonghong)
Daniel Borkmann (6):
bpf: improve bpf_redirect_neigh helper description
bpf: add redirect_peer helper
bpf: allow for map-in-map with dynamic inner array map entries
bpf, selftests: add test for different array inner map size
bpf, selftests: make redirect_neigh test more extensible
bpf, selftests: add redirect_peer selftest
drivers/net/veth.c | 9 +
include/linux/bpf.h | 2 +-
include/linux/netdevice.h | 4 +
include/uapi/linux/bpf.h | 32 ++-
kernel/bpf/arraymap.c | 17 +-
kernel/bpf/hashtab.c | 6 +-
kernel/bpf/verifier.c | 4 +-
net/core/dev.c | 15 +-
net/core/filter.c | 54 ++++-
net/xdp/xskmap.c | 2 +-
tools/include/uapi/linux/bpf.h | 32 ++-
.../selftests/bpf/prog_tests/btf_map_in_map.c | 39 +++-
.../selftests/bpf/progs/test_btf_map_in_map.c | 43 ++++
.../selftests/bpf/progs/test_tc_neigh.c | 40 ++--
.../selftests/bpf/progs/test_tc_peer.c | 45 ++++
tools/testing/selftests/bpf/test_tc_neigh.sh | 168 ---------------
.../testing/selftests/bpf/test_tc_redirect.sh | 204 ++++++++++++++++++
17 files changed, 492 insertions(+), 224 deletions(-)
create mode 100644 tools/testing/selftests/bpf/progs/test_tc_peer.c
delete mode 100755 tools/testing/selftests/bpf/test_tc_neigh.sh
create mode 100755 tools/testing/selftests/bpf/test_tc_redirect.sh
--
2.17.1
next reply other threads:[~2020-10-09 20:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 20:42 Daniel Borkmann [this message]
2020-10-09 20:42 ` [PATCH bpf-next v3 1/6] bpf: improve bpf_redirect_neigh helper description Daniel Borkmann
2020-10-09 20:42 ` [PATCH bpf-next v3 2/6] bpf: add redirect_peer helper Daniel Borkmann
2020-10-09 20:42 ` [PATCH bpf-next v3 3/6] bpf: allow for map-in-map with dynamic inner array map entries Daniel Borkmann
2020-10-09 21:04 ` Alexei Starovoitov
2020-10-09 21:09 ` Daniel Borkmann
2020-10-09 20:42 ` [PATCH bpf-next v3 4/6] bpf, selftests: add test for different array inner map size Daniel Borkmann
2020-10-09 20:42 ` [PATCH bpf-next v3 5/6] bpf, selftests: make redirect_neigh test more extensible Daniel Borkmann
2020-10-09 20:42 ` [PATCH bpf-next v3 6/6] bpf, selftests: add redirect_peer selftest Daniel Borkmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201009204245.27905-1-daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=yhs@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).