From: patchwork-bot+netdevbpf@kernel.org
To: Amery Hung <ameryhung@gmail.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
alexei.starovoitov@gmail.com, andrii@kernel.org,
daniel@iogearbox.net, tj@kernel.org, martin.lau@kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH bpf-next v8 0/6] Support associating BPF programs with struct_ops
Date: Sat, 06 Dec 2025 00:59:12 +0000 [thread overview]
Message-ID: <176498275203.1878807.11776031951947151435.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251203233748.668365-1-ameryhung@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 3 Dec 2025 15:37:42 -0800 you wrote:
> Hi,
>
> This patchset adds a new BPF command BPF_PROG_ASSOC_STRUCT_OPS to
> the bpf() syscall to allow associating a BPF program with a struct_ops.
> The command is introduced to address a emerging need from struct_ops
> users. As the number of subsystems adopting struct_ops grows, more
> users are building their struct_ops-based solution with some help from
> other BPF programs. For example, scx_layer uses a syscall program as
> a user space trigger to refresh layers [0]. It also uses tracing program
> to infer whether a task is using GPU and needs to be prioritized [1]. In
> these use cases, when there are multiple struct_ops instances, the
> struct_ops kfuncs called from different BPF programs, whether struct_ops
> or not needs to be able to refer to a specific one, which currently is
> not possible.
>
> [...]
Here is the summary with links:
- [bpf-next,v8,1/6] bpf: Allow verifier to fixup kernel module kfuncs
https://git.kernel.org/bpf/bpf-next/c/1588c81b9f21
- [bpf-next,v8,2/6] bpf: Support associating BPF program with struct_ops
https://git.kernel.org/bpf/bpf-next/c/b5709f6d26d6
- [bpf-next,v8,3/6] libbpf: Add support for associating BPF program with struct_ops
https://git.kernel.org/bpf/bpf-next/c/87cd177b149a
- [bpf-next,v8,4/6] selftests/bpf: Test BPF_PROG_ASSOC_STRUCT_OPS command
https://git.kernel.org/bpf/bpf-next/c/33a165f9c2c1
- [bpf-next,v8,5/6] selftests/bpf: Test ambiguous associated struct_ops
https://git.kernel.org/bpf/bpf-next/c/04fd12df4e05
- [bpf-next,v8,6/6] selftests/bpf: Test getting associated struct_ops in timer callback
https://git.kernel.org/bpf/bpf-next/c/0e841d19263a
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:[~2025-12-06 1:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 23:37 [PATCH bpf-next v8 0/6] Support associating BPF programs with struct_ops Amery Hung
2025-12-03 23:37 ` [PATCH bpf-next v8 1/6] bpf: Allow verifier to fixup kernel module kfuncs Amery Hung
2025-12-03 23:57 ` bot+bpf-ci
2025-12-03 23:37 ` [PATCH bpf-next v8 2/6] bpf: Support associating BPF program with struct_ops Amery Hung
2025-12-03 23:37 ` [PATCH bpf-next v8 3/6] libbpf: Add support for " Amery Hung
2025-12-03 23:57 ` bot+bpf-ci
2025-12-03 23:37 ` [PATCH bpf-next v8 4/6] selftests/bpf: Test BPF_PROG_ASSOC_STRUCT_OPS command Amery Hung
2025-12-03 23:37 ` [PATCH bpf-next v8 5/6] selftests/bpf: Test ambiguous associated struct_ops Amery Hung
2025-12-03 23:37 ` [PATCH bpf-next v8 6/6] selftests/bpf: Test getting associated struct_ops in timer callback Amery Hung
2025-12-06 0:59 ` 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=176498275203.1878807.11776031951947151435.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@meta.com \
--cc=martin.lau@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tj@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