Messages in this thread | | | Date | Thu, 19 Oct 2006 00:03:03 -0700 | From | Paul Jackson <> | Subject | Re: [RFC] Cpuset: explicit dynamic sched domain control flags |
| |
Nick wrote: > You don't have to worry about the details of the hierarchy. You just need > to know where the partitions are
Cpusets is a hierarchical space. What happens in a subtree of the /dev/cpuset hierarchy should not be affecting others.
Partitioning sched domains is a flat space - dividing the CPUs of a system into disjoint partitions.
Using details deep in the cpuset hierarchy to define global partitions leads to chaos in the minds of those coming at this from the cpuset side.
The lack of any means on a production system to view the resulting partition leads to ignorance of how deep is the chaos, a dangerous state of affairs.
-- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <pj@sgi.com> 1.925.600.0401 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |