Re: exclusive cpusets broken with cpu hotplug

[Nick Piggin <nickpiggin@yahoo.com.au>]

Siddha, Suresh B wrote:
> On Wed, Oct 18, 2006 at 10:16:50PM +1000, Nick Piggin wrote:
> 
>>Paul Jackson wrote:
>>
>>> 1) I don't know how to tell what sched domains/groups a system has, nor
> 
> 
> Paul, atleast for debugging one can know that by defining SCHED_DOMAIN_DEBUG

Yep. This is meant to be useful precisely for things like making cpusets
partition the domains properly or ensuring a system's topology is built
correctly.

>>>    how to tell my customers how to see what sched domains they have, and
>>
>>I don't know if you want customers do know what domains they have. I think
> 
> 
> At the first glance, I have to agree with Nick. All the customer wants is a
> mechanism to specify group these cpus together for scheduling...
> 
> But looking at how cpusets interact with sched-domains and especially for
> large systems, it will probably be useful if we export the topology through /sys

I'll concede that point. It would probably be useful for a sysadmin to be
able to look at how they can better make cpuset placements such that they
get the best partitioning.

I would still prefer not to say "use an exclusive domain for this cpuset".
cpusets should be able to do the optimal thing with the data it has, so
this is one less complication to deal with.

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com