public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizefan@huawei.com>
To: Tejun Heo <tj@kernel.org>
Cc: <mingo@redhat.com>, <a.p.zijlstra@chello.nl>, <paulus@samba.org>,
	<acme@ghostprotocols.net>, <eranian@google.com>,
	<namhyung.kim@lge.com>, <mhocko@suse.cz>,
	<kamezawa.hiroyu@jp.fujitsu.com>, <cgroups@vger.kernel.org>,
	<containers@lists.linux-foundation.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCHSET] perf, cgroup: implement hierarchy support for perf_event controller
Date: Tue, 9 Apr 2013 15:07:56 +0800	[thread overview]
Message-ID: <5163BE4C.5040301@huawei.com> (raw)
In-Reply-To: <1365474213-13354-1-git-send-email-tj@kernel.org>

On 2013/4/9 10:23, Tejun Heo wrote:
> perf_event cgroup controller is one of the remaining few with broken
> hierarchy support.  It turns out it's pretty easy to implement - the
> only thing necessary is making perf_cgroup_match() return %true also
> when the cgroup of the current task is a descendant of the event's
> cgroup.  This patchset implements cgroup_is_descendant() and uses it
> to implement hierarchy support in perf_event controller.
> 
> This patchset contains the following three patches.
> 
>  0001-cgroup-make-sure-parent-won-t-be-destroyed-before-it.patch
>  0002-cgroup-implement-cgroup_is_descendant.patch
>  0003-perf-make-perf_event-cgroup-hierarchical.patch
> 
> The patches are also available in the following git branch, which is
> based on top of cgroup/for-3.10.  It's currently based on top of
> cgroup/for-3.10 as the first patch causes non-trivial conflict with it
> otherwise, which is not difficult to resolve but still nice to avoid
> anyway.
> 
> Li, Michal, I picked the first two patches from Li's memcg patchset.
> Can we push the first two through cgroup/for-3.10 and put the rest in
> -mm?
> 

Sure. Andrew asked me to resend the memcg patchset when we are at 3.10-rc1,
because 3.9-rc6 is a bit too late and he's too busy.

> Ingo, how should these be routed?


  parent reply	other threads:[~2013-04-09  7:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09  2:23 [PATCHSET] perf, cgroup: implement hierarchy support for perf_event controller Tejun Heo
2013-04-09  2:23 ` [PATCH 1/3] cgroup: make sure parent won't be destroyed before its children Tejun Heo
2013-04-09  2:23 ` [PATCH 2/3] cgroup: implement cgroup_is_descendant() Tejun Heo
2013-04-09  2:23 ` [PATCH 3/3] perf: make perf_event cgroup hierarchical Tejun Heo
2013-04-09  7:07 ` Li Zefan [this message]
2013-04-10  7:32 ` [PATCHSET] perf, cgroup: implement hierarchy support for perf_event controller Peter Zijlstra
2013-04-10  9:37   ` Ingo Molnar
2013-04-10 18:01     ` Tejun Heo
2013-04-10 18:08 ` Tejun Heo

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=5163BE4C.5040301@huawei.com \
    --to=lizefan@huawei.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=cgroups@vger.kernel.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=eranian@google.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=mingo@redhat.com \
    --cc=namhyung.kim@lge.com \
    --cc=paulus@samba.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