From: patchwork-bot+netdevbpf@kernel.org
To: Delyan Kratunov <delyank@fb.com>
Cc: daniel@iogearbox.net, ast@kernel.org, andrii@kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v4 0/5] Subskeleton support for BPF libraries
Date: Fri, 18 Mar 2022 06:20:11 +0000 [thread overview]
Message-ID: <164758441135.25738.7426516446576821597.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1647473511.git.delyank@fb.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 16 Mar 2022 23:37:26 +0000 you wrote:
> In the quest for ever more modularity, a new need has arisen - the ability to
> access data associated with a BPF library from a corresponding userspace library.
> The catch is that we don't want the userspace library to know about the structure of the
> final BPF object that the BPF library is linked into.
>
> In pursuit of this modularity, this patch series introduces *subskeletons.*
> Subskeletons are similar in use and design to skeletons with a couple of differences:
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/5] libbpf: .text routines are subprograms in strict mode
https://git.kernel.org/bpf/bpf-next/c/bc380eb9d048
- [bpf-next,v4,4/5] bpftool: add support for subskeletons
https://git.kernel.org/bpf/bpf-next/c/00389c58ffe9
- [bpf-next,v4,2/5] libbpf: init btf_{key,value}_type_id on internal map open
https://git.kernel.org/bpf/bpf-next/c/262cfb74ffda
- [bpf-next,v4,5/5] selftests/bpf: test subskeleton functionality
https://git.kernel.org/bpf/bpf-next/c/3cccbaa03321
- [bpf-next,v4,3/5] libbpf: add subskeleton scaffolding
https://git.kernel.org/bpf/bpf-next/c/430025e5dca5
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:[~2022-03-18 6:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 23:37 [PATCH bpf-next v4 0/5] Subskeleton support for BPF libraries Delyan Kratunov
2022-03-16 23:37 ` [PATCH bpf-next v4 1/5] libbpf: .text routines are subprograms in strict mode Delyan Kratunov
2022-03-16 23:37 ` [PATCH bpf-next v4 4/5] bpftool: add support for subskeletons Delyan Kratunov
2022-03-16 23:37 ` [PATCH bpf-next v4 2/5] libbpf: init btf_{key,value}_type_id on internal map open Delyan Kratunov
2022-03-16 23:37 ` [PATCH bpf-next v4 5/5] selftests/bpf: test subskeleton functionality Delyan Kratunov
2022-03-16 23:37 ` [PATCH bpf-next v4 3/5] libbpf: add subskeleton scaffolding Delyan Kratunov
2022-03-17 23:34 ` [PATCH bpf-next v4 0/5] Subskeleton support for BPF libraries Andrii Nakryiko
2022-03-18 6: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=164758441135.25738.7426516446576821597.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=delyank@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox