Re: [PATCH] task containersv11 add tasks file interface fix for cpusets

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Paul Jackson <pj@...>
Cc: <akpm@...>, <nickpiggin@...>, <a.p.zijlstra@...>, <serue@...>, <clg@...>, <linux-kernel@...>, <ebiederm@...>, <rientjes@...>, <svaidy@...>, <xemul@...>, <containers@...>, <balbir@...>
Date: Wednesday, October 3, 2007 - 2:10 pm

On 10/3/07, Paul Jackson <pj@sgi.com> wrote:

What's the rationale for this?

Given that later in cpusets.txt you say:


why can't the same thing be done when changing the 'cpus' file manually.

What's wrong with, in update_cpumask(), doing a loop across all
members of the cgroup and updating their cpus_allowed fields?

The existing cpusets API is broken, since a new child can always be
forked between reading the tasks file and doing the writes.

Paul
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [PATCH] task containersv11 add tasks file interface fix ..., Paul Menage, (Wed Oct 3, 2:10 pm)
Re: [PATCH] task containersv11 add tasks file interface fix ..., Eric W. Biederman, (Thu Oct 11, 7:20 pm)