[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6599ad830710030851jb44f00ft9634f9381218b6e9@mail.gmail.com>
Date: Wed, 3 Oct 2007 08:51:41 -0700
From: "Paul Menage" <menage@...gle.com>
To: "Paul Jackson" <pj@....com>
Cc: "Andrew Morton" <akpm@...ux-foundation.org>,
"Nick Piggin" <nickpiggin@...oo.com.au>,
"Peter Zijlstra" <a.p.zijlstra@...llo.nl>,
"Serge E. Hallyn" <serue@...ibm.com>,
"Cedric Le Goater" <clg@...ibm.com>, linux-kernel@...r.kernel.org,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"David Rientjes" <rientjes@...gle.com>,
"Vaidyanathan Srinivasan" <svaidy@...ux.vnet.ibm.com>,
"Pavel Emelianov" <xemul@...nvz.org>, containers@...ts.osdl.org,
balbir@...ux.vnet.ibm.com
Subject: Re: [PATCH] task containersv11 add tasks file interface fix for cpusets
On 10/3/07, Paul Jackson <pj@....com> wrote:
> From: Paul Jackson <pj@....com>
>
> The code in kernel/cgroup.c attach_task() which skips the
> attachment of a task to the group it is already in has to be
> removed. Cpusets depends on reattaching a task to its current
> cpuset, in order to trigger updating the cpus_allowed mask in the
> task struct.
Can you explain a bit more about why this is needed? (i.e. specific
scenarios where cpusets will break without this change).
What triggers the reattach in normal use? Something from userspace?
Paul
-
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