From: Donglin Peng <dolinux.peng@gmail.com>
To: ast@kernel.org
Cc: linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
Donglin Peng <dolinux.peng@gmail.com>
Subject: [RFC PATCH v2 0/5] Significantly Improve BTF Type Lookup Performance
Date: Mon, 20 Oct 2025 17:39:36 +0800 [thread overview]
Message-ID: <20251020093941.548058-1-dolinux.peng@gmail.com> (raw)
The funcgraph-args feature currently invokes btf_find_by_name_kind()
frequently, which uses a linear search algorithm. With large BTF data
sets like vmlinux (containing over 80,000 named types), this results
in significant performance overhead.
This patch series optimizes btf_find_by_name_kind() by:
1. Sorting BTF types by kind and name to enable binary search
2. Changing the search order to check local BTF before base BTF
Performance testing shows dramatic improvement:
# echo 1 > options/funcgraph-args
# echo function_graph > current_tracer
Before:
# time cat trace | wc -l
124176
real 0m16.154s
user 0m0.000s
sys 0m15.962s
After:
# time cat trace | wc -l
124176
real 0m0.948s
user 0m0.000s
sys 0m0.973s
This represents over 20x performance improvement for BTF type lookups.
Donglin Peng (5):
btf: search local BTF before base BTF
btf: sort BTF types by kind and name to enable binary search
libbpf: check if BTF is sorted to enable binary search
selftests/bpf: add tests for BTF deduplication and sorting
btf: add CONFIG_BPF_SORT_BTF_BY_KIND_NAME
include/linux/btf.h | 21 ++-
kernel/bpf/Kconfig | 8 +
kernel/bpf/Makefile | 1 +
kernel/bpf/btf.c | 36 ++--
kernel/bpf/btf_sort.c | 2 +
scripts/Makefile.btf | 5 +
tools/lib/bpf/Build | 2 +-
tools/lib/bpf/btf.c | 169 +++++++++++++++---
tools/lib/bpf/btf.h | 2 +
tools/lib/bpf/btf_sort.c | 159 +++++++++++++++++
tools/lib/bpf/libbpf_internal.h | 6 +
tools/testing/selftests/bpf/prog_tests/btf.c | 171 +++++++++++++++++++
12 files changed, 541 insertions(+), 41 deletions(-)
create mode 100644 kernel/bpf/btf_sort.c
create mode 100644 tools/lib/bpf/btf_sort.c
--
2.34.1
next reply other threads:[~2025-10-20 9:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 9:39 Donglin Peng [this message]
2025-10-20 9:39 ` [RFC PATCH v2 1/5] btf: search local BTF before base BTF Donglin Peng
2025-10-21 1:06 ` Eduard Zingerman
2025-10-21 8:31 ` Donglin Peng
2025-10-21 15:56 ` Eduard Zingerman
2025-10-22 3:08 ` Donglin Peng
2025-10-20 9:39 ` [RFC PATCH v2 2/5] btf: sort BTF types by kind and name to enable binary search Donglin Peng
2025-10-21 17:24 ` Alan Maguire
2025-10-22 4:47 ` Donglin Peng
2025-10-21 18:59 ` Eduard Zingerman
2025-10-22 3:02 ` Donglin Peng
2025-10-22 20:50 ` Eduard Zingerman
2025-10-23 10:35 ` Donglin Peng
2025-10-23 15:52 ` Alexei Starovoitov
2025-10-23 16:28 ` Andrii Nakryiko
2025-10-23 18:37 ` Alexei Starovoitov
2025-10-23 19:39 ` Andrii Nakryiko
2025-10-24 1:59 ` Donglin Peng
2025-10-24 2:23 ` Donglin Peng
2025-10-24 2:32 ` Eduard Zingerman
2025-10-24 3:04 ` Donglin Peng
2025-10-24 3:15 ` Eduard Zingerman
2025-10-24 3:19 ` Donglin Peng
2025-10-20 9:39 ` [RFC PATCH v2 3/5] libbpf: check if BTF is sorted " Donglin Peng
2025-10-20 9:39 ` [RFC PATCH v2 4/5] selftests/bpf: add tests for BTF deduplication and sorting Donglin Peng
2025-10-21 19:07 ` Eduard Zingerman
2025-10-23 11:20 ` Donglin Peng
2025-10-20 9:39 ` [RFC PATCH v2 5/5] btf: add CONFIG_BPF_SORT_BTF_BY_KIND_NAME Donglin Peng
2025-10-21 0:50 ` Eduard Zingerman
2025-10-21 8:33 ` Donglin Peng
2025-10-21 17:27 ` Alan Maguire
2025-10-22 1:15 ` Donglin Peng
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=20251020093941.548058-1-dolinux.peng@gmail.com \
--to=dolinux.peng@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@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).