From: Hou Tao <houtao1@huawei.com>
To: Alexei Starovoitov <ast@kernel.org>
Cc: Martin KaFai Lau <kafai@fb.com>, Yonghong Song <yhs@fb.com>,
Song Liu <songliubraving@fb.com>,
Daniel Borkmann <daniel@iogearbox.net>,
"Andrii Nakryiko" <andrii@kernel.org>, <netdev@vger.kernel.org>,
<bpf@vger.kernel.org>, <houtao1@huawei.com>
Subject: [RFC PATCH bpf-next 0/2] introduce bpf_strncmp() helper
Date: Sat, 6 Nov 2021 21:28:20 +0800 [thread overview]
Message-ID: <20211106132822.1396621-1-houtao1@huawei.com> (raw)
Hi,
The motivation for introducing bpf_strncmp() helper comes from
two aspects:
(1) clang doesn't always replace strncmp() automatically
(and don't known why)
In tracing program, sometimes we need to using a home-made
strncmp() to check whether or not the file name is expected.
(2) the performance of home-made strncmp is not so good
As shown in the benchmark of patch #2, the performance of
bpf_strncmp helper is 80% better than home-made strncmp under
x86-64, and 600% better under arm64 thanks to its arch-optimized
strncmp().
But i'm concernt about whether the API of bpf_strncmp() is OK.
Now the first argument must be a read-only null-terminated
string, it is enough for our file-name comparsion case because
the target file name is const and read-only, but may be not
usable for comparsion of two strings stored in writable-maps.
Any comments are welcome.
Regards,
Tao
Hou Tao (2):
bpf: add bpf_strncmp helper
selftests/bpf: add benchmark bpf_strcmp
include/linux/bpf.h | 1 +
include/uapi/linux/bpf.h | 11 ++
kernel/bpf/helpers.c | 14 +++
kernel/trace/bpf_trace.c | 2 +
tools/include/uapi/linux/bpf.h | 11 ++
.../bpf/prog_tests/test_strncmp_helper.c | 75 ++++++++++++
.../selftests/bpf/progs/strncmp_helper.c | 109 ++++++++++++++++++
7 files changed, 223 insertions(+)
create mode 100644 tools/testing/selftests/bpf/prog_tests/test_strncmp_helper.c
create mode 100644 tools/testing/selftests/bpf/progs/strncmp_helper.c
--
2.29.2
next reply other threads:[~2021-11-06 13:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-06 13:28 Hou Tao [this message]
2021-11-06 13:28 ` [RFC PATCH bpf-next 1/2] bpf: add bpf_strncmp helper Hou Tao
2021-11-06 19:26 ` Alexei Starovoitov
2021-11-06 20:07 ` Andrii Nakryiko
2021-11-06 20:32 ` Alexei Starovoitov
2021-11-08 14:08 ` Hou Tao
2021-11-08 13:45 ` Hou Tao
2021-11-06 13:28 ` [RFC PATCH bpf-next 2/2] selftests/bpf: add benchmark bpf_strcmp Hou Tao
2021-11-06 18:43 ` Alexei Starovoitov
2021-11-08 14:05 ` Hou Tao
2021-11-08 18:00 ` 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=20211106132822.1396621-1-houtao1@huawei.com \
--to=houtao1@huawei.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--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).