[patch] CFS scheduler, -v7

[Ingo Molnar]

i'm pleased to announce release -v7 of the CFS scheduler patchset. (The 
main goal of CFS is to implement "desktop scheduling" with as high 
quality as technically possible.)

The CFS patch against v2.6.21 (or against v2.6.20.8) can be downloaded 
from the usual place:

    http://redhat.com/~mingo/cfs-scheduler/

-v6 got lots of nice feedback and the -v5 list of regressions has shrunk 
considerably. The most user-visible change in -v7 should be a fix for an 
interactivity problem that should/could explain the 'audio skipping' 
problem reported by Kasper Sandberg. (which was the only main regression 
reported against -v6. Please re-report regressions, if any.)

the rate of change is moderate:

    15 files changed, 150 insertions(+), 124 deletions(-)

half of that code-flux is due to the removal of the X auto-renice patch 
and most of the rest is debugging related. It seems the CFS codebase is 
slowly starting to settle down. (-v7 has been test-built and test-booted 
on i686 and x86_64 UP and SMP systems.)

Changes since -v6:

 - speedup: cache rb_leftmost better (Srivatsa Vaddagiri)

 - bugfix: handle Priority Inheritance properly (Thomas Gleixner)

 - interactivity fix: tighten up arithmetics some more.

 - feature removal: remove the X auto-renicing feature, CONFIG_BOOST_X.

 - debugging feature: introduce the sched_sleep_history_max_ns tunable
   to modify sleep-history handling.

 - debugging feature: /proc/<PID>/sched file contains various useful
   scheduler statistics about every task.

 - debugging feature: track the maximum amount of time a task has been
   waiting to get on the CPU, the maximum amount of time it was blocked
   involuntarily and the maximum amount of time it was sleeping
   voluntarily.

As usual, any sort of feedback, bugreport, fix and suggestion is more 
than welcome,

	Ingo
-
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/