From: patchwork-bot+netdevbpf@kernel.org
To: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kafai@meta.com, kernel-team@meta.com,
eddyz87@gmail.com, yatsenko@meta.com, emil@etsalapatis.com
Subject: Re: [PATCH bpf-next v4 0/3] libbpf: Add bpf_program__clone() for individual program loading
Date: Sat, 21 Mar 2026 20:20:28 +0000 [thread overview]
Message-ID: <177412442853.2951219.12560475166355057636.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260317-veristat_prepare-v4-0-74193d4cc9d9@meta.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 17 Mar 2026 10:39:20 -0700 you wrote:
> This series adds bpf_program__clone() to libbpf and converts veristat to
> use it, replacing the costly per-program object re-opening pattern.
>
> veristat needs to load each BPF program in isolation to collect
> per-program verification statistics. Previously it achieved this by
> opening a fresh bpf_object for every program, disabling autoload on all
> but the target, and loading the whole object. For object files with many
> programs this meant repeating ELF parsing and BTF processing N times.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/3] libbpf: Introduce bpf_program__clone()
https://git.kernel.org/bpf/bpf-next/c/970bd2dced35
- [bpf-next,v4,2/3] selftests/bpf: Use bpf_program__clone() in veristat
https://git.kernel.org/bpf/bpf-next/c/3be706b937f3
- [bpf-next,v4,3/3] selftests/bpf: Test bpf_program__clone() attach_btf_id override
https://git.kernel.org/bpf/bpf-next/c/ceebdeec6e8c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-03-21 20:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 17:39 [PATCH bpf-next v4 0/3] libbpf: Add bpf_program__clone() for individual program loading Mykyta Yatsenko
2026-03-17 17:39 ` [PATCH bpf-next v4 1/3] libbpf: Introduce bpf_program__clone() Mykyta Yatsenko
2026-03-17 19:40 ` Emil Tsalapatis
2026-03-17 17:39 ` [PATCH bpf-next v4 2/3] selftests/bpf: Use bpf_program__clone() in veristat Mykyta Yatsenko
2026-03-17 17:39 ` [PATCH bpf-next v4 3/3] selftests/bpf: Test bpf_program__clone() attach_btf_id override Mykyta Yatsenko
2026-03-17 19:50 ` Emil Tsalapatis
2026-03-21 20:20 ` patchwork-bot+netdevbpf [this message]
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=177412442853.2951219.12560475166355057636.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=kafai@meta.com \
--cc=kernel-team@meta.com \
--cc=mykyta.yatsenko5@gmail.com \
--cc=yatsenko@meta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.