From: Alexei Starovoitov <ast@kernel.org>
To: <davem@davemloft.net>
Cc: <daniel@iogearbox.net>, <netdev@vger.kernel.org>,
<bpf@vger.kernel.org>, <kernel-team@fb.com>
Subject: [PATCH bpf-next 0/3] bpf: increase jmp sequence limit
Date: Tue, 21 May 2019 16:09:36 -0700 [thread overview]
Message-ID: <20190521230939.2149151-1-ast@kernel.org> (raw)
Patch 1 - jmp sequence limit
Patch 2 - improve existing tests
Patch 3 - add pyperf-based realistic bpf program that takes advantage
of higher limit and use it as a stress test
Alexei Starovoitov (3):
bpf: bump jmp sequence limit
selftests/bpf: adjust verifier scale test
selftests/bpf: add pyperf scale test
kernel/bpf/verifier.c | 7 +-
.../bpf/prog_tests/bpf_verif_scale.c | 31 +-
tools/testing/selftests/bpf/progs/pyperf.h | 268 ++++++++++++++++++
tools/testing/selftests/bpf/progs/pyperf100.c | 4 +
tools/testing/selftests/bpf/progs/pyperf180.c | 4 +
tools/testing/selftests/bpf/progs/pyperf50.c | 4 +
tools/testing/selftests/bpf/test_verifier.c | 31 +-
7 files changed, 319 insertions(+), 30 deletions(-)
create mode 100644 tools/testing/selftests/bpf/progs/pyperf.h
create mode 100644 tools/testing/selftests/bpf/progs/pyperf100.c
create mode 100644 tools/testing/selftests/bpf/progs/pyperf180.c
create mode 100644 tools/testing/selftests/bpf/progs/pyperf50.c
--
2.20.0
next reply other threads:[~2019-05-21 23:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 23:09 Alexei Starovoitov [this message]
2019-05-21 23:09 ` [PATCH bpf-next 1/3] bpf: bump jmp sequence limit Alexei Starovoitov
2019-05-21 23:09 ` [PATCH bpf-next 2/3] selftests/bpf: adjust verifier scale test Alexei Starovoitov
2019-05-21 23:09 ` [PATCH bpf-next 3/3] selftests/bpf: add pyperf " Alexei Starovoitov
2019-05-22 0:36 ` Andrii Nakryiko
2019-05-22 0:49 ` Alexei Starovoitov
2019-05-22 0:56 ` Andrii Nakryiko
2019-05-22 0:37 ` [PATCH bpf-next 0/3] bpf: increase jmp sequence limit 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=20190521230939.2149151-1-ast@kernel.org \
--to=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.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;
as well as URLs for NNTP newsgroup(s).