From: Song Liu <songliubraving@fb.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@redhat.com>, Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Stephane Eranian <eranian@google.com>,
Andi Kleen <ak@linux.intel.com>,
"Ian Rogers" <irogers@google.com>, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH 1/2] perf/core: Share an event with multiple cgroups
Date: Thu, 1 Apr 2021 06:19:19 +0000 [thread overview]
Message-ID: <8C7049AE-A3B8-48C2-8A4B-FB5CADE95F6B@fb.com> (raw)
In-Reply-To: <CAM9d7chtYw0v49Q5ue6B=D_8kV6ZyMvT7p10_jxsHMc+H309tA@mail.gmail.com>
> On Mar 30, 2021, at 8:11 AM, Namhyung Kim <namhyung@kernel.org> wrote:
>
> On Tue, Mar 30, 2021 at 3:33 PM Song Liu <songliubraving@fb.com> wrote:
>>> On Mar 29, 2021, at 4:33 AM, Namhyung Kim <namhyung@kernel.org> wrote:
>>>
>>> On Mon, Mar 29, 2021 at 2:17 AM Song Liu <songliubraving@fb.com> wrote:
>>>>> On Mar 23, 2021, at 9:21 AM, Namhyung Kim <namhyung@kernel.org> wrote:
>>>>>
>>>>> As we can run many jobs (in container) on a big machine, we want to
>>>>> measure each job's performance during the run. To do that, the
>>>>> perf_event can be associated to a cgroup to measure it only.
>>>>>
>>
>> [...]
>>
>>>>> + return 0;
>>>>> +}
>>>>
>>>> Could you please explain why we need this logic in can_attach?
>>>
>>> IIUC the ss->attach() is called after a task's cgroup membership
>>> is changed. But we want to collect the performance numbers for
>>> the old cgroup just before the change. As the logic merely checks
>>> the current task's cgroup, it should be done in the can_attach()
>>> which is called before the cgroup change.
>>
>> Thanks for the explanations.
>>
>> Overall, I really like the core idea, especially that the overhead on
>> context switch is bounded (by the depth of cgroup tree).
>
> Thanks!
>
>>
>> Is it possible to make PERF_EVENT_IOC_ATTACH_CGROUP more flexible?
>> Specifically, if we can have
>>
>> PERF_EVENT_IOC_ADD_CGROUP add a cgroup to the list
>> PERF_EVENT_IOC_EL_CGROUP delete a cgroup from the list
>>
>> we can probably share these events among multiple processes, and
>> these processes don't need to know others' cgroup list. I think
>> this will be useful for users to build customized monitoring in
>> its own container.
>>
>> Does this make sense?
>
> Maybe we can add ADD/DEL interface for more flexible monitoring
> but I'm not sure which use cases it'll be used actually.
>
> For your multi-process sharing case, the original events' file
> descriptors should be shared first.
Yes, we will need some other work to make the ADD/DEL interface
work properly. Let's worry about that later.
For both patches:
Acked-by: Song Liu <songliubraving@fb.com>
Thanks,
Song
[...]
next prev parent reply other threads:[~2021-04-01 6:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 16:21 [RFC 0/2] perf core: Sharing events " Namhyung Kim
2021-03-23 16:21 ` [PATCH 1/2] perf/core: Share an event " Namhyung Kim
2021-03-24 0:30 ` Song Liu
2021-03-24 1:06 ` Namhyung Kim
2021-03-25 0:55 ` Song Liu
2021-03-25 2:44 ` Namhyung Kim
2021-03-25 12:57 ` Arnaldo Carvalho de Melo
2021-03-28 17:17 ` Song Liu
2021-03-29 11:33 ` Namhyung Kim
2021-03-30 6:33 ` Song Liu
2021-03-30 15:11 ` Namhyung Kim
2021-04-01 6:00 ` Stephane Eranian
2021-04-01 6:19 ` Song Liu [this message]
2021-03-23 16:21 ` [PATCH 2/2] perf/core: Support reading group events with shared cgroups Namhyung Kim
2021-03-28 17:31 ` Song Liu
2021-03-29 11:36 ` Namhyung Kim
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=8C7049AE-A3B8-48C2-8A4B-FB5CADE95F6B@fb.com \
--to=songliubraving@fb.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tj@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
all inboxes | Powered by JetHome®