From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: davem@davemloft.net
Cc: daniel@iogearbox.net, bpf@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH v2 bpf-next 0/7] bpf: Misc improvements
Date: Sat, 6 Feb 2021 09:03:37 -0800 [thread overview]
Message-ID: <20210206170344.78399-1-alexei.starovoitov@gmail.com> (raw)
From: Alexei Starovoitov <ast@kernel.org>
Several improvements:
- optimize prog stats
- compute stats for sleepable progs
- prevent recursion fentry/fexit and sleepable progs
- allow map-in-map and per-cpu maps in sleepable progs
Alexei Starovoitov (7):
bpf: Optimize program stats
bpf: Compute program stats for sleepable programs
bpf: Add per-program recursion prevention mechanism
selftest/bpf: Add a recursion test
bpf: Count the number of times recursion was prevented
bpf: Allows per-cpu maps and map-in-map in sleepable programs
selftests/bpf: Add a test for map-in-map and per-cpu maps in sleepable
progs
arch/x86/net/bpf_jit_comp.c | 46 ++++++++-----
include/linux/bpf.h | 16 ++---
include/linux/filter.h | 12 +++-
include/uapi/linux/bpf.h | 1 +
kernel/bpf/core.c | 16 +++--
kernel/bpf/hashtab.c | 4 +-
kernel/bpf/syscall.c | 16 +++--
kernel/bpf/trampoline.c | 59 +++++++++++++---
kernel/bpf/verifier.c | 9 ++-
tools/bpf/bpftool/prog.c | 5 ++
tools/include/uapi/linux/bpf.h | 1 +
.../selftests/bpf/prog_tests/fexit_stress.c | 2 +-
.../selftests/bpf/prog_tests/recursion.c | 33 +++++++++
.../bpf/prog_tests/trampoline_count.c | 4 +-
tools/testing/selftests/bpf/progs/lsm.c | 69 +++++++++++++++++++
tools/testing/selftests/bpf/progs/recursion.c | 46 +++++++++++++
16 files changed, 282 insertions(+), 57 deletions(-)
create mode 100644 tools/testing/selftests/bpf/prog_tests/recursion.c
create mode 100644 tools/testing/selftests/bpf/progs/recursion.c
--
2.24.1
next reply other threads:[~2021-02-06 17:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 17:03 Alexei Starovoitov [this message]
2021-02-06 17:03 ` [PATCH v2 bpf-next 1/7] bpf: Optimize program stats Alexei Starovoitov
2021-02-08 18:57 ` Andrii Nakryiko
2021-02-08 21:28 ` Daniel Borkmann
2021-02-08 23:13 ` Alexei Starovoitov
2021-02-09 0:53 ` Daniel Borkmann
2021-02-06 17:03 ` [PATCH v2 bpf-next 2/7] bpf: Compute program stats for sleepable programs Alexei Starovoitov
2021-02-08 20:35 ` Andrii Nakryiko
2021-02-06 17:03 ` [PATCH v2 bpf-next 3/7] bpf: Add per-program recursion prevention mechanism Alexei Starovoitov
2021-02-08 20:51 ` Andrii Nakryiko
2021-02-09 19:06 ` Alexei Starovoitov
2021-02-09 19:15 ` Andrii Nakryiko
2021-02-06 17:03 ` [PATCH v2 bpf-next 4/7] selftest/bpf: Add a recursion test Alexei Starovoitov
2021-02-08 20:54 ` Andrii Nakryiko
2021-02-06 17:03 ` [PATCH v2 bpf-next 5/7] bpf: Count the number of times recursion was prevented Alexei Starovoitov
2021-02-08 20:58 ` Andrii Nakryiko
2021-02-06 17:03 ` [PATCH v2 bpf-next 6/7] bpf: Allows per-cpu maps and map-in-map in sleepable programs Alexei Starovoitov
2021-02-08 21:00 ` Andrii Nakryiko
2021-02-08 21:01 ` Andrii Nakryiko
2021-02-08 23:20 ` Alexei Starovoitov
2021-02-06 17:03 ` [PATCH v2 bpf-next 7/7] selftests/bpf: Add a test for map-in-map and per-cpu maps in sleepable progs Alexei Starovoitov
2021-02-08 21:04 ` Andrii Nakryiko
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=20210206170344.78399-1-alexei.starovoitov@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kernel-team@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