[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180706140304.6de698a9@cakuba.netronome.com>
Date: Fri, 6 Jul 2018 14:03:04 -0700
From: Jakub Kicinski <jakub.kicinski@...ronome.com>
To: Roman Gushchin <guro@...com>
Cc: <netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<kernel-team@...com>,
Quentin Monnet <quentin.monnet@...ronome.com>,
Daniel Borkmann <daniel@...earbox.net>,
Alexei Starovoitov <ast@...nel.org>,
David Ahern <dsahern@...il.com>
Subject: Re: [PATCH bpf-next 1/2] bpftool: introduce cgroup tree command
On Fri, 6 Jul 2018 11:25:45 -0700, Roman Gushchin wrote:
> > Looks very useful! Minor nits/questions below. I think the reverse
> > mapping could also be interesting - similar to how -f flag shows where
> > program is pinned, we could add a flag which in
> >
> > # bpftool prog show/list
> >
> > adds info about cgroups where the program is attached? Obviously as a
> > future extension.
>
> Well, it would be convenient, but it's not always possible.
> A program can be attached to a dying cgroup (a cgroup which was deleted
> by a user, but still has some associated resources, e.g. pagecache).
Ack, the bpffs and cgroupfs searches are best effort by definition.
Thanks for addressing the other comments!
Powered by blists - more mailing lists