From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yhs@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, kpsingh@kernel.org,
martin.lau@kernel.org, tj@kernel.org
Subject: Re: [PATCH bpf-next v6 0/9] bpf: Implement cgroup local storage available to non-cgroup-attached bpf progs
Date: Wed, 26 Oct 2022 06:40:18 +0000 [thread overview]
Message-ID: <166676641845.4978.11078534978845698275.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221026042835.672317-1-yhs@fb.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 25 Oct 2022 21:28:35 -0700 you wrote:
> There already exists a local storage implementation for cgroup-attached
> bpf programs. See map type BPF_MAP_TYPE_CGROUP_STORAGE and helper
> bpf_get_local_storage(). But there are use cases such that non-cgroup
> attached bpf progs wants to access cgroup local storage data. For example,
> tc egress prog has access to sk and cgroup. It is possible to use
> sk local storage to emulate cgroup local storage by storing data in socket.
> But this is a waste as it could be lots of sockets belonging to a particular
> cgroup. Alternatively, a separate map can be created with cgroup id as the key.
> But this will introduce additional overhead to manipulate the new map.
> A cgroup local storage, similar to existing sk/inode/task storage,
> should help for this use case.
>
> [...]
Here is the summary with links:
- [bpf-next,v6,1/9] bpf: Make struct cgroup btf id global
https://git.kernel.org/bpf/bpf-next/c/5e67b8ef125b
- [bpf-next,v6,2/9] bpf: Refactor some inode/task/sk storage functions for reuse
https://git.kernel.org/bpf/bpf-next/c/c83597fa5dc6
- [bpf-next,v6,3/9] bpf: Implement cgroup storage available to non-cgroup-attached bpf progs
https://git.kernel.org/bpf/bpf-next/c/c4bcfb38a95e
- [bpf-next,v6,4/9] libbpf: Support new cgroup local storage
https://git.kernel.org/bpf/bpf-next/c/4fe64af23c12
- [bpf-next,v6,5/9] bpftool: Support new cgroup local storage
https://git.kernel.org/bpf/bpf-next/c/f7f0f1657d95
- [bpf-next,v6,6/9] selftests/bpf: Fix test test_libbpf_str/bpf_map_type_str
https://git.kernel.org/bpf/bpf-next/c/fd4ca6c1facf
- [bpf-next,v6,7/9] selftests/bpf: Add selftests for new cgroup local storage
https://git.kernel.org/bpf/bpf-next/c/12bb6ca4e2fa
- [bpf-next,v6,8/9] selftests/bpf: Add test cgrp_local_storage to DENYLIST.s390x
https://git.kernel.org/bpf/bpf-next/c/0a1b69d1c736
- [bpf-next,v6,9/9] docs/bpf: Add documentation for new cgroup local storage
https://git.kernel.org/bpf/bpf-next/c/d43198017ea3
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-10-26 6:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 4:28 [PATCH bpf-next v6 0/9] bpf: Implement cgroup local storage available to non-cgroup-attached bpf progs Yonghong Song
2022-10-26 4:28 ` [PATCH bpf-next v6 1/9] bpf: Make struct cgroup btf id global Yonghong Song
2022-10-26 4:28 ` [PATCH bpf-next v6 2/9] bpf: Refactor some inode/task/sk storage functions for reuse Yonghong Song
2022-10-26 4:28 ` [PATCH bpf-next v6 3/9] bpf: Implement cgroup storage available to non-cgroup-attached bpf progs Yonghong Song
2022-10-26 4:28 ` [PATCH bpf-next v6 4/9] libbpf: Support new cgroup local storage Yonghong Song
2022-10-26 4:29 ` [PATCH bpf-next v6 5/9] bpftool: " Yonghong Song
2022-10-26 4:29 ` [PATCH bpf-next v6 6/9] selftests/bpf: Fix test test_libbpf_str/bpf_map_type_str Yonghong Song
2022-10-26 4:29 ` [PATCH bpf-next v6 7/9] selftests/bpf: Add selftests for new cgroup local storage Yonghong Song
2022-10-26 4:29 ` [PATCH bpf-next v6 8/9] selftests/bpf: Add test cgrp_local_storage to DENYLIST.s390x Yonghong Song
2022-10-26 4:29 ` [PATCH bpf-next v6 9/9] docs/bpf: Add documentation for new cgroup local storage Yonghong Song
2022-10-26 6:40 ` 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=166676641845.4978.11078534978845698275.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=kernel-team@fb.com \
--cc=kpsingh@kernel.org \
--cc=martin.lau@kernel.org \
--cc=tj@kernel.org \
--cc=yhs@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