sched: update comment

update comment: clarify time-slices and remove obsolete tuning detail.

Signed-off-by: Ingo Molnar <mingo@elte.hu>
This commit is contained in:
Ingo Molnar 2007-10-15 17:00:14 +02:00
parent 95938a35c5
commit d274a4cee1

View file

@ -25,14 +25,12 @@
* (default: 20ms, units: nanoseconds) * (default: 20ms, units: nanoseconds)
* *
* NOTE: this latency value is not the same as the concept of * NOTE: this latency value is not the same as the concept of
* 'timeslice length' - timeslices in CFS are of variable length. * 'timeslice length' - timeslices in CFS are of variable length
* (to see the precise effective timeslice length of your workload, * and have no persistent notion like in traditional, time-slice
* run vmstat and monitor the context-switches field) * based scheduling concepts.
* *
* On SMP systems the value of this is multiplied by the log2 of the * (to see the precise effective timeslice length of your workload,
* number of CPUs. (i.e. factor 2x on 2-way systems, 3x on 4-way * run vmstat and monitor the context-switches (cs) field)
* systems, 4x on 8-way systems, 5x on 16-way systems, etc.)
* Targeted preemption latency for CPU-bound tasks:
*/ */
const_debug unsigned int sysctl_sched_latency = 20000000ULL; const_debug unsigned int sysctl_sched_latency = 20000000ULL;