[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6599ad830710031115g3a45e996j30bd7b5e8d77a035@mail.gmail.com>
Date: Wed, 3 Oct 2007 11:15:57 -0700
From: "Paul Menage" <menage@...gle.com>
To: "Paul Jackson" <pj@....com>
Cc: akpm@...ux-foundation.org, balbir@...ux.vnet.ibm.com,
serue@...ibm.com, clg@...ibm.com, ebiederm@...ssion.com,
xemul@...nvz.org, rientjes@...gle.com, svaidy@...ux.vnet.ibm.com,
nickpiggin@...oo.com.au, a.p.zijlstra@...llo.nl,
containers@...ts.osdl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 03/33] task containersv11 add tasks file interface
On 10/3/07, Paul Jackson <pj@....com> wrote:
>
> So after changing the 'cpus' of a cpuset, you (something in
> user space) then has to rewrite every pid in that cpusets
> tasks file back to that same tasks file, in order to get the
> change to be applied to each of those tasks, and get them to
> start running on their new CPUs.
What happens to the new child that got forked right between userspace
reading the 'tasks' file and writing back the pids?
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