From: Yonghong Song <yhs@fb.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: <ast@fb.com>, <daniel@iogearbox.net>, <netdev@vger.kernel.org>,
<kernel-team@fb.com>
Subject: Re: [PATCH net-next 0/3] bpf: implement bpf_get_current_cgroup_id() helper
Date: Sun, 3 Jun 2018 16:03:09 -0700 [thread overview]
Message-ID: <2630312d-d5eb-6cc1-e96b-ddb66d81c781@fb.com> (raw)
In-Reply-To: <20180603195959.jvo54so66mhkpvww@ast-mbp>
On 6/3/18 1:00 PM, Alexei Starovoitov wrote:
> On Sun, Jun 03, 2018 at 12:36:51AM -0700, Yonghong Song wrote:
>> bpf has been used extensively for tracing. For example, bcc
>> contains an almost full set of bpf-based tools to trace kernel
>> and user functions/events. Most tracing tools are currently
>> either filtered based on pid or system-wide.
>>
>> Containers have been used quite extensively in industry and
>> cgroup is often used together to provide resource isolation
>> and protection. Several processes may run inside the same
>> container. It is often desirable to get container-level tracing
>> results as well, e.g. syscall count, function count, I/O
>> activity, etc.
>>
>> This patch implements a new helper, bpf_get_current_cgroup_id(),
>> which will return cgroup id based on the cgroup within which
>> the current task is running.
>>
>> Patch #1 implements the new helper in the kernel.
>> Patch #2 syncs the uapi bpf.h header and helper between tools
>> and kernel.
>> Patch #3 shows how to get the same cgroup id in user space,
>> so a filter or policy could be configgured in the bpf program
>> based on current task cgroup.
>
> for all patches:
> Acked-by: Alexei Starovoitov <ast@kernel.org>
>
> please rebase, so it can be applied and s/net-next/bpf-next/ in subj.
Sorry. Missed to change subject line from "net-next" to "bpf-next".
Do you want to submit another revision?
> Thanks!
>
prev parent reply other threads:[~2018-06-03 23:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-03 7:36 [PATCH net-next 0/3] bpf: implement bpf_get_current_cgroup_id() helper Yonghong Song
2018-06-03 7:36 ` [PATCH net-next 1/3] " Yonghong Song
2018-06-03 7:36 ` [PATCH net-next 2/3] tools/bpf: sync uapi bpf.h for " Yonghong Song
2018-06-03 7:36 ` [PATCH net-next 3/3] tools/bpf: add a selftest " Yonghong Song
2018-06-03 20:00 ` [PATCH net-next 0/3] bpf: implement " Alexei Starovoitov
2018-06-03 23:03 ` Yonghong Song [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=2630312d-d5eb-6cc1-e96b-ddb66d81c781@fb.com \
--to=yhs@fb.com \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).