I wrote:
The Linux CFS scheduler prefers pinned tasks and unfairly
gives more CPU time to tasks that have set CPU affinity.
...
I believe I have now solved the problem, simply by setting:
for n in /proc/sys/kernel/sched_domain/cpu*/domain0/min_interval; do echo 0
> $n; done
for n in /proc/sys/kernel/sched_domain/cpu*/domain0/max_interval; do echo 1
> $n; done
Testing with real-life jobs, I found I needed min_- and max_interval for
domain1 also, and a couple of other non-default values, so:
for n in /proc/sys/kernel/sched_domain/cpu*/dom*/min_interval; do echo 0 >
$n; done
for n in /proc/sys/kernel/sched_domain/cpu*/dom*/max_interval; do echo 1 >
$n; done
echo 1000000000 > /proc/sys/kernel/sched_latency_ns
echo 100000 > /proc/sys/kernel/sched_min_granularity_ns
echo 10000 > /proc/sys/kernel/sched_wakeup_granularity_ns
and then things seem fair and my users are happy.
Thanks, Paul
Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics University of Sydney Australia
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
