From: Andrii Nakryiko <andriin@fb.com>
To: <bpf@vger.kernel.org>, <netdev@vger.kernel.org>, <ast@fb.com>,
<daniel@iogearbox.net>
Cc: <andrii.nakryiko@gmail.com>, <kernel-team@fb.com>,
Andrii Nakryiko <andriin@fb.com>
Subject: [PATCH v2 bpf-next 0/3] Add benchmark runner and few benchmarks
Date: Fri, 8 May 2020 16:20:29 -0700 [thread overview]
Message-ID: <20200508232032.1974027-1-andriin@fb.com> (raw)
Add generic benchmark runner framework which simplifies writing various
performance benchmarks in a consistent fashion. This framework will be used
in follow up patches to test performance of perf buffer and ring buffer as
well.
Patch #1 adds generic runner implementation and atomic counter benchmarks to
validate benchmark runner's behavior.
Patch #2 implements test_overhead benchmark as part of bench runner. It also
add fmod_ret BPF program type to a set of benchmarks.
Patch #3 tests faster alternatives to set_task_comm() approach, tested in
test_overhead, in search for minimal-overhead way to trigger BPF program
execution from user-space on demand.
v1->v2:
- moved benchmarks into benchs/ subdir (John);
- added benchmark "suite" scripts (John);
- few small clean ups, change defaults, etc.
Andrii Nakryiko (3):
selftests/bpf: add benchmark runner infrastructure
selftest/bpf: fmod_ret prog and implement test_overhead as part of
bench
selftest/bpf: add BPF triggering benchmark
tools/testing/selftests/bpf/.gitignore | 1 +
tools/testing/selftests/bpf/Makefile | 17 +-
tools/testing/selftests/bpf/bench.c | 398 ++++++++++++++++++
tools/testing/selftests/bpf/bench.h | 74 ++++
.../selftests/bpf/benchs/bench_count.c | 91 ++++
.../selftests/bpf/benchs/bench_rename.c | 195 +++++++++
.../selftests/bpf/benchs/bench_trigger.c | 167 ++++++++
.../selftests/bpf/benchs/run_bench_rename.sh | 9 +
.../selftests/bpf/benchs/run_bench_trigger.sh | 9 +
.../selftests/bpf/prog_tests/test_overhead.c | 14 +-
.../selftests/bpf/progs/test_overhead.c | 6 +
.../selftests/bpf/progs/trigger_bench.c | 47 +++
12 files changed, 1026 insertions(+), 2 deletions(-)
create mode 100644 tools/testing/selftests/bpf/bench.c
create mode 100644 tools/testing/selftests/bpf/bench.h
create mode 100644 tools/testing/selftests/bpf/benchs/bench_count.c
create mode 100644 tools/testing/selftests/bpf/benchs/bench_rename.c
create mode 100644 tools/testing/selftests/bpf/benchs/bench_trigger.c
create mode 100755 tools/testing/selftests/bpf/benchs/run_bench_rename.sh
create mode 100755 tools/testing/selftests/bpf/benchs/run_bench_trigger.sh
create mode 100644 tools/testing/selftests/bpf/progs/trigger_bench.c
--
2.24.1
next reply other threads:[~2020-05-08 23:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 23:20 Andrii Nakryiko [this message]
2020-05-08 23:20 ` [PATCH v2 bpf-next 1/3] selftests/bpf: add benchmark runner infrastructure Andrii Nakryiko
2020-05-09 17:10 ` Yonghong Song
2020-05-12 3:29 ` Andrii Nakryiko
2020-05-12 14:39 ` Yonghong Song
2020-05-08 23:20 ` [PATCH v2 bpf-next 2/3] selftest/bpf: fmod_ret prog and implement test_overhead as part of bench Andrii Nakryiko
2020-05-09 17:23 ` Yonghong Song
2020-05-12 4:22 ` Andrii Nakryiko
2020-05-12 15:11 ` Yonghong Song
2020-05-12 17:23 ` Andrii Nakryiko
2020-05-12 17:47 ` Yonghong Song
2020-05-08 23:20 ` [PATCH v2 bpf-next 3/3] selftest/bpf: add BPF triggering benchmark Andrii Nakryiko
2020-05-09 17:43 ` Yonghong Song
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=20200508232032.1974027-1-andriin@fb.com \
--to=andriin@fb.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
/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