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
> > 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
> cpusets is the only thing that messes with sched-domains (excluding the
> isolcpus -- that seems to require a small change to partition_sched_domains,
> but forget that for now).
> And so you should know what partitioning to build at any point when asked.
> So we could have a call to cpusets at the end of arch_init_sched_domains,
> which asks for the domains to be partitioned, no?
Robin, Right now everyone is calling arch_init_sched_domain() with
cpu_online_map. We can remove this argument and in the presence of cpusets,
this routine can go through exclusive cpusets and partition the domains
accordinly. Otherwise we can simply build one domain partition with
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Video 4 Linux]
[Linux for the blind]