From: Yonghong Song <yhs@fb.com>
To: Hao Luo <haoluo@google.com>,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>, KP Singh <kpsingh@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
Stanislav Fomichev <sdf@google.com>, Jiri Olsa <jolsa@kernel.org>,
Yosry Ahmed <yosryahmed@google.com>,
Quentin Monnet <quentin@isovalent.com>
Subject: Re: [PATCH bpf-next v1] bpftool: Add support for querying cgroup_iter link
Date: Tue, 30 Aug 2022 09:41:06 -0700 [thread overview]
Message-ID: <c84fa46d-8f37-c449-06ea-5da795f091e8@fb.com> (raw)
In-Reply-To: <20220829231828.1016835-1-haoluo@google.com>
On 8/29/22 4:18 PM, Hao Luo 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
>
>> bpftool -p link show
> [{
> "id": 1,
> "type": "iter",
> "prog_id": 2,
> "target_name": "bpf_map"
> },{
> "id": 2,
> "type": "iter",
> "prog_id": 3,
> "target_name": "bpf_prog"
> },{
> "id": 3,
> "type": "iter",
> "prog_id": 12,
> "target_name": "cgroup",
> "cgroup_id": 72,
> "order": "self_only"
> }
> ]
>
> Signed-off-by: Hao Luo <haoluo@google.com>
Acked-by: Yonghong Song <yhs@fb.com>
next prev parent reply other threads:[~2022-08-30 16:41 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 [this message]
2022-08-30 18:20 ` Hao Luo
2022-08-30 18:10 ` patchwork-bot+netdevbpf
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=c84fa46d-8f37-c449-06ea-5da795f091e8@fb.com \
--to=yhs@fb.com \
--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=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