From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org,
tj@kernel.org
Subject: Re: [PATCH bpf-next v12 0/7] bpf: Support private stack for bpf progs
Date: Wed, 13 Nov 2024 01:20:32 +0000 [thread overview]
Message-ID: <173146083249.741480.16435519636826517152.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241112163902.2223011-1-yonghong.song@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 12 Nov 2024 08:39:02 -0800 you wrote:
> The main motivation for private stack comes from nested scheduler in
> sched-ext from Tejun. The basic idea is that
> - each cgroup will its own associated bpf program,
> - bpf program with parent cgroup will call bpf programs
> in immediate child cgroups.
>
> Let us say we have the following cgroup hierarchy:
> root_cg (prog0):
> cg1 (prog1):
> cg11 (prog11):
> cg111 (prog111)
> cg112 (prog112)
> cg12 (prog12):
> cg121 (prog121)
> cg122 (prog122)
> cg2 (prog2):
> cg21 (prog21)
> cg22 (prog22)
> cg23 (prog23)
>
> [...]
Here is the summary with links:
- [bpf-next,v12,1/7] bpf: Find eligible subprogs for private stack support
https://git.kernel.org/bpf/bpf-next/c/a76ab5731e32
- [bpf-next,v12,2/7] bpf: Enable private stack for eligible subprogs
https://git.kernel.org/bpf/bpf-next/c/e00931c02568
- [bpf-next,v12,3/7] bpf, x86: Avoid repeated usage of bpf_prog->aux->stack_depth
https://git.kernel.org/bpf/bpf-next/c/f4b21ed0b9d6
- [bpf-next,v12,4/7] bpf, x86: Support private stack in jit
https://git.kernel.org/bpf/bpf-next/c/7d1cd70d4b16
- [bpf-next,v12,5/7] selftests/bpf: Add tracing prog private stack tests
https://git.kernel.org/bpf/bpf-next/c/f4b295ab6598
- [bpf-next,v12,6/7] bpf: Support private stack for struct_ops progs
https://git.kernel.org/bpf/bpf-next/c/5bd36da1e37e
- [bpf-next,v12,7/7] selftests/bpf: Add struct_ops prog private stack tests
https://git.kernel.org/bpf/bpf-next/c/becfe32b57c7
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:[~2024-11-13 1:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 16:39 [PATCH bpf-next v12 0/7] bpf: Support private stack for bpf progs Yonghong Song
2024-11-12 16:39 ` [PATCH bpf-next v12 1/7] bpf: Find eligible subprogs for private stack support Yonghong Song
2024-11-12 16:39 ` [PATCH bpf-next v12 2/7] bpf: Enable private stack for eligible subprogs Yonghong Song
2024-11-12 16:39 ` [PATCH bpf-next v12 3/7] bpf, x86: Avoid repeated usage of bpf_prog->aux->stack_depth Yonghong Song
2024-11-12 16:39 ` [PATCH bpf-next v12 4/7] bpf, x86: Support private stack in jit Yonghong Song
2024-11-13 1:13 ` Alexei Starovoitov
2024-11-13 4:32 ` Yonghong Song
2024-11-12 16:39 ` [PATCH bpf-next v12 5/7] selftests/bpf: Add tracing prog private stack tests Yonghong Song
2024-11-12 16:39 ` [PATCH bpf-next v12 6/7] bpf: Support private stack for struct_ops progs Yonghong Song
2024-11-12 16:39 ` [PATCH bpf-next v12 7/7] selftests/bpf: Add struct_ops prog private stack tests Yonghong Song
2024-11-13 1: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=173146083249.741480.16435519636826517152.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=martin.lau@kernel.org \
--cc=tj@kernel.org \
--cc=yonghong.song@linux.dev \
/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