Re: scheduler scalability - cgroups, cpusets andload-balancing

[Gregory Haskins]

>>> On Tue, Jan 29, 2008 at  4:02 PM, in message
<20080129150234.b57ce988.pj@xxxxxxx>, Paul Jackson <pj@xxxxxxx> wrote: 
> Gregory wrote:
>> > ... (1) turning off
>> > sched_load_balance in any overlapping cpusets, including all
>> > encompassing parent cpusets, (2) leaving sched_load_balance on in the
>> > RT cpuset itself, and ...
>>
>> Technically you only need (2).  I run my 4-8 core development systems
>> in the single default global cpuset, normally.
> 
> Well, if you're running in the default cpuset, then you automatically get 
> (1),
> because sched_load_balance is turned off in all overlapping cpusets (there
> aren't any overlapping cpusets!)
> 
> So, yes, you -do- need both (1) and (2).  In your normal system, you
> just happen to get (1) effortlessly.


Ah.  Well see, I am just showing my ignorance of this area of the cpuset code then.  I stand corrected, and sorry for the noise. :)

-Greg

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/