Messages in this thread | | | Date | Thu, 19 Oct 2006 01:31:30 -0700 | From | Paul Jackson <> | Subject | Re: exclusive cpusets broken with cpu hotplug |
| |
> So make the new rule "cpu_exclusive && direct-child-of-root-cpuset". > Your problems go away, and they haven't been pushed to userspace.
I don't know of anyone that has need for this feature.
Do you? If you do - good - lets consider them anew.
If such needs arise, I doubt I would recommend meeting them with the cpu_exclusive flag, in any way shape or form. That would probably not be a particularly clear and intuitive interface for whatever it was we needed.
> If a user wants to, for some crazy reason, have a set of cpu_exclusive > sets deep in the cpuset hierarchy, such that no load balancing happens > between them... just tell them they can't; they should just make those > cpusets children of the root.
I have no problem telling users what the limits are on mechanisms.
I have serious problems trying to push mechanisms on them that I couldn't understand until after repeated attempts over many months, that are counter intuitive and dangerous (at least unless such odd rules are imposed) to use, and that provide no useful feedback to the user as to what they are doing.
It doesn't increase my sympathy for this code that it has been my biggest source of customer maintenance costs due to a couple of serious bugs, in all of the cpuset code.
-- 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/
| |