[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111014152110.GN14968@somewhere>
Date: Fri, 14 Oct 2011 17:21:13 +0200
From: Frederic Weisbecker <fweisbec@...il.com>
To: Ben Blum <bblum@...rew.cmu.edu>
Cc: Tejun Heo <tj@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Oleg Nesterov <oleg@...hat.com>, linux-kernel@...r.kernel.org,
NeilBrown <neilb@...e.de>, paulmck@...ux.vnet.ibm.com,
Paul Menage <paul@...lmenage.org>,
Li Zefan <lizf@...fujitsu.com>,
containers@...ts.linux-foundation.org,
Balbir Singh <bsingharora@...il.com>,
Daisuke Nishimura <nishimura@....nes.nec.co.jp>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Subject: Re: [PATCH 2/2] cgroups: convert ss->attach to use whole threadgroup
flex_array (cpuset, memcontrol)
On Fri, Oct 14, 2011 at 09:53:23AM -0400, Ben Blum wrote:
> On Fri, Oct 14, 2011 at 02:21:30PM +0200, Frederic Weisbecker wrote:
> > On Thu, Oct 13, 2011 at 08:36:01PM -0400, Ben Blum wrote:
> > > Convert ss->attach to take a flex_array of tasks instead of just the leader.
> > >
> > > From: Ben Blum <bblum@...rew.cmu.edu>
> > >
> > > This lets subsystems with whole-threadgroup attach calls (i.e., cpuset and
> > > memcontrol) to accurately find the group's mm even when a non-leader does exec
> > > and leaves the leader with a NULL mm pointer.
> > >
> > > Also converts cpuset and memcontrol to take the flex_array and iterate down it
> > > until an mm is found, instead of just attempting to use the leader's mm.
> > >
> > > Signed-off-by: Ben Blum <bblum@...rew.cmu.edu>
> >
> > I think there are patches from Tejun that handle that did that already?
> >
> > https://lkml.org/lkml/2011/8/23/418
> >
>
> Yeah, I'm not hoping to preempt them or anything; I'm just presenting
> this alternate approach, since (1) this way addresses the ss->attach()
> problem directly without needing to add locking anywhere else
You basically have the same approach, the locking involved in Tejun's
patches seem to address a different issue that you would need to
address as well anyway.
> , while the
> focus of the discussion around Tejun's patches seems to have moved to
> more global concerns, and (2) these patches and his patches ought to be
> compatible with each other.
But Tejun's patches seem to address not only your issue but even more.
I don't understand the point of this lighter version.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists