Messages in this thread | | | Date | Wed, 12 Mar 2008 14:32:53 -0500 | From | Paul Jackson <> | Subject | Re: boot cgroup questions |
| |
Max wrote: > I was talking about running on the _cpus_ that belong to the "sets A and B but > not C" and not that a task must belong to more than one cpuset.
This doesn't make sense to me.
If a task is to run on the CPUs in both sets A and B, then it has to be in both those cpusets, which isn't allowed, or in some super set of both A and B (that is, in this example, in the top cpuset), which doesn't restrict the task to just A or B or their union.
I have no idea what distinction you are seeing between what _cpus_ a task can run on, and what cpuset it belongs to.
-- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <pj@sgi.com> 1.940.382.4214
| |