From: Jakub Sitnicki <jakub@cloudflare.com>
To: Andrey Grodzovsky <andrey.grodzovsky@crowdstrike.com>
Cc: <bpf@vger.kernel.org>, <linux-open-source@crowdstrike.com>,
<ast@kernel.org>, <daniel@iogearbox.net>, <andrii@kernel.org>,
<jolsa@kernel.org>, <rostedt@goodmis.org>,
<linux-trace-kernel@vger.kernel.org>,
<kernel-team@cloudflare.com>
Subject: Re: [RFC PATCH bpf-next v3 0/3] Optimize kprobe.session attachment for exact function names
Date: Mon, 02 Mar 2026 13:47:58 +0100 [thread overview]
Message-ID: <87o6l6e6td.fsf@cloudflare.com> (raw)
In-Reply-To: <20260227204052.725813-1-andrey.grodzovsky@crowdstrike.com> (Andrey Grodzovsky's message of "Fri, 27 Feb 2026 15:40:49 -0500")
On Fri, Feb 27, 2026 at 03:40 PM -05, Andrey Grodzovsky wrote:
> - Patch 1: libbpf detects exact function names (no wildcards) in
> bpf_program__attach_kprobe_multi_opts() and bypasses kallsyms parsing,
> passing the symbol directly to the kernel via syms[] array.
> ESRCH is normalized to ENOENT for API consistency.
FWIW, Ivan was also trying to make it faster from the kernel side:
https://lore.kernel.org/bpf/20260129-ivan-bpf-ksym-cache-v1-1-ca503070dcc0@cloudflare.com/
But, IIUC, with this change we're not hitting get_ksymbol_bpf at all.
next prev parent reply other threads:[~2026-03-02 12:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 20:40 [RFC PATCH bpf-next v3 0/3] Optimize kprobe.session attachment for exact function names Andrey Grodzovsky
2026-02-27 20:40 ` [RFC PATCH bpf-next v3 1/3] libbpf: " Andrey Grodzovsky
2026-02-27 21:17 ` bot+bpf-ci
2026-02-27 22:28 ` [External] " Andrey Grodzovsky
2026-03-02 10:58 ` Jiri Olsa
2026-03-02 17:37 ` Andrey Grodzovsky
2026-02-27 20:40 ` [RFC PATCH bpf-next v3 2/3] ftrace: Use kallsyms binary search for single-symbol lookup Andrey Grodzovsky
2026-02-27 20:40 ` [RFC PATCH bpf-next v3 3/3] selftests/bpf: add tests for kprobe.session optimization Andrey Grodzovsky
2026-02-27 20:43 ` [RFC PATCH bpf-next v3 0/3] Optimize kprobe.session attachment for exact function names Alexei Starovoitov
2026-02-27 21:15 ` [External] " Andrey Grodzovsky
2026-03-02 19:25 ` Jakub Sitnicki
2026-03-02 19:47 ` Andrey Grodzovsky
2026-03-02 12:47 ` Jakub Sitnicki [this message]
2026-03-02 18:00 ` Andrey Grodzovsky
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=87o6l6e6td.fsf@cloudflare.com \
--to=jakub@cloudflare.com \
--cc=andrey.grodzovsky@crowdstrike.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jolsa@kernel.org \
--cc=kernel-team@cloudflare.com \
--cc=linux-open-source@crowdstrike.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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