All of lore.kernel.org
 help / color / mirror / Atom feed
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
Subject: Re: [PATCH bpf-next v5 0/5] bpf: Implement mprog API on top of existing cgroup progs
Date: Mon, 09 Jun 2025 23:40:36 +0000	[thread overview]
Message-ID: <174951243600.1592300.9068365275620223473.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250606163131.2428225-1-yonghong.song@linux.dev>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Fri,  6 Jun 2025 09:31:31 -0700 you wrote:
> Current cgroup prog ordering is appending at attachment time. This is not
> ideal. In some cases, users want specific ordering at a particular cgroup
> level. For example, in Meta, we have a case where three different
> applications all have cgroup/setsockopt progs and they require specific
> ordering. Current approach is to use a bpfchainer where one bpf prog
> contains multiple global functions and each global function can be
> freplaced by a prog for a specific application. The ordering of global
> functions decides the ordering of those application specific bpf progs.
> Using bpfchainer is a centralized approach and is not desirable as
> one of applications acts as a daemon. The decentralized attachment
> approach is more favorable for those applications.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v5,1/5] cgroup: Add bpf prog revisions to struct cgroup_bpf
    https://git.kernel.org/bpf/bpf-next/c/9b8367b604c7
  - [bpf-next,v5,2/5] bpf: Implement mprog API on top of existing cgroup progs
    (no matching commit)
  - [bpf-next,v5,3/5] libbpf: Support link-based cgroup attach with options
    https://git.kernel.org/bpf/bpf-next/c/1d6711667cb3
  - [bpf-next,v5,4/5] selftests/bpf: Move some tc_helpers.h functions to test_progs.h
    https://git.kernel.org/bpf/bpf-next/c/c1bb68656bc1
  - [bpf-next,v5,5/5] selftests/bpf: Add two selftests for mprog API based cgroup progs
    https://git.kernel.org/bpf/bpf-next/c/e422d5f118e4

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-06-09 23:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-06 16:31 [PATCH bpf-next v5 0/5] bpf: Implement mprog API on top of existing cgroup progs Yonghong Song
2025-06-06 16:31 ` [PATCH bpf-next v5 1/5] cgroup: Add bpf prog revisions to struct cgroup_bpf Yonghong Song
2025-06-06 16:31 ` [PATCH bpf-next v5 2/5] bpf: Implement mprog API on top of existing cgroup progs Yonghong Song
2025-06-09 23:35   ` Andrii Nakryiko
2025-06-10  1:20     ` Yonghong Song
2025-06-10 15:46       ` Andrii Nakryiko
2025-06-06 16:31 ` [PATCH bpf-next v5 3/5] libbpf: Support link-based cgroup attach with options Yonghong Song
2025-06-06 16:31 ` [PATCH bpf-next v5 4/5] selftests/bpf: Move some tc_helpers.h functions to test_progs.h Yonghong Song
2025-06-06 16:31 ` [PATCH bpf-next v5 5/5] selftests/bpf: Add two selftests for mprog API based cgroup progs Yonghong Song
2025-06-09 23: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=174951243600.1592300.9068365275620223473.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=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 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.