From: patchwork-bot+netdevbpf@kernel.org
To: Hao Luo <haoluo@google.com>
Cc: linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
kpsingh@kernel.org, john.fastabend@gmail.com, sdf@google.com,
jolsa@kernel.org, yosryahmed@google.com, quentin@isovalent.com
Subject: Re: [PATCH bpf-next v1] bpftool: Add support for querying cgroup_iter link
Date: Tue, 30 Aug 2022 18:10:14 +0000 [thread overview]
Message-ID: <166188301427.32674.16752744307188143944.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220829231828.1016835-1-haoluo@google.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@linux.dev>:
On Mon, 29 Aug 2022 16:18:28 -0700 you wrote:
> Support dumping info of a cgroup_iter link. This includes
> showing the cgroup's id and the order for walking the cgroup
> hierarchy. Example output is as follows:
>
> > bpftool link show
> 1: iter prog 2 target_name bpf_map
> 2: iter prog 3 target_name bpf_prog
> 3: iter prog 12 target_name cgroup cgroup_id 72 order self_only
>
> [...]
Here is the summary with links:
- [bpf-next,v1] bpftool: Add support for querying cgroup_iter link
https://git.kernel.org/bpf/bpf-next/c/6f95de6d7131
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-08-30 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 23:18 [PATCH bpf-next v1] bpftool: Add support for querying cgroup_iter link Hao Luo
2022-08-30 13:33 ` Quentin Monnet
2022-08-30 18:06 ` Martin KaFai Lau
2022-08-30 18:19 ` Hao Luo
2022-08-30 16:41 ` Yonghong Song
2022-08-30 18:20 ` Hao Luo
2022-08-30 18:10 ` 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=166188301427.32674.16752744307188143944.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=quentin@isovalent.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yhs@fb.com \
--cc=yosryahmed@google.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