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, memxor@gmail.com,
martin.lau@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v2 0/3] Allow struct_ops to create map id to
Date: Wed, 06 Aug 2025 23:20:11 +0000 [thread overview]
Message-ID: <175452241100.2973132.16950481472519463981.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250806162540.681679-1-ameryhung@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Wed, 6 Aug 2025 09:25:37 -0700 you wrote:
> v1 -> v2
> Add bpf_struct_ops_id() instead of using bpf_struct_ops_get()
>
> Hi,
>
> This patchset allows struct_ops implementors to get map id from kdata in
> reg(), unreg() and update() so that they create an id to struct_ops
> instance mapping. This in turn allows struct_ops kfuncs to refer to the
> calling instance without passing a pointer to the struct_ops. The selftest
> provides an end-to-end example.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/3] bpf: Allow struct_ops to get map id by kdata
https://git.kernel.org/bpf/bpf-next/c/d87a513d0937
- [bpf-next,v2,2/3] selftests/bpf: Add multi_st_ops that supports multiple instances
https://git.kernel.org/bpf/bpf-next/c/eeb52b6279cf
- [bpf-next,v2,3/3] selftests/bpf: Test multi_st_ops and calling kfuncs from different programs
https://git.kernel.org/bpf/bpf-next/c/ba7000f1c360
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-08-06 23:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 16:25 [PATCH bpf-next v2 0/3] Allow struct_ops to create map id to Amery Hung
2025-08-06 16:25 ` [PATCH bpf-next v2 1/3] bpf: Allow struct_ops to get map id by kdata Amery Hung
2025-08-06 16:25 ` [PATCH bpf-next v2 2/3] selftests/bpf: Add multi_st_ops that supports multiple instances Amery Hung
2025-08-06 23:16 ` Martin KaFai Lau
2025-08-06 16:25 ` [PATCH bpf-next v2 3/3] selftests/bpf: Test multi_st_ops and calling kfuncs from different programs Amery Hung
2025-08-06 23:20 ` Martin KaFai Lau
2025-08-06 23: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=175452241100.2973132.16950481472519463981.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=memxor@gmail.com \
--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 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.