[lkml]   [2006]   [Oct]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC] cpuset: Explicit dynamic sched domain cpuset flag
pj wrote:
> 9) Finally, we really do need a way, on a production system, for user
> space to ask the kernel where load balancing is limited.
> For example one possible interface would have user space pass a
> cpumask to the kernel, and get back a Boolean value, indicating
> whether or not there are any limitations on load balancing between
> any two CPUs specified in that cpumask.

Ah - a simpler API, more user friendly, more "cpuset API style"

A read-only, per-cpuset Boolean flag that indicates whether the
scheduler is fully load balancing across all 'cpus' of that cpuset.

Internally, the kernel would answer this by seeing whether or
not the cpusets cpus_allowed cpumask was a subset of one of the
members of the scheduler domains partition.

Call this per-cpuset flag something such as:

sched_is_fully_load_balanced # read-only Boolean

This goes along with having the control flag named something such as:

sched_ok_not_to_load_balance # read-write Boolean

If a task was in a cpuset that had 'sched_is_fully_load_balanced'
False, then it might not get load balanced.

I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <> 1.925.600.0401
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-11-01 01:01    [W:0.037 / U:3.120 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site