<http://prdownloads.sourceforge.net/cpuse/plugsched-2.0-for-2.6.10.pat...>

as a single patch to linux-2.6.10 and at:

<http://prdownloads.sourceforge.net/cpuse/plugsched-2.0-for-2.6.10.pat...>

as a (gzipped and tarred) patch set including "series" file which
nominates the order of application of the patches.

This is an update of the earlier version of plugsched (previously
released by Con Kolivas) and has a considerably modified scheduler
interface that is intended to reduce the amount of code duplication
required when adding a new scheduler.  It also contains a sysfs
interface based on work submitted by Chris Han.

This version of plugsched contains 4 schedulers:

1. "ingosched" which is the standard active/expired array O(1) scheduler
created by Ingo Molnar,
2. "staircase" which is Con Kolivas's version 10.5 O(1) staircase scheduler,
3. "spa_no_frills" which is a single priority array O(1) scheduler
without any interactive response enhancements, etc., and
4. "zaphod" which is a single priority array O(1) scheduler with
interactive response bonuses, throughput bonuses and a choice of
priority based or entitlement based interpretation of "nice".

Schedulers 3 and 4 also offer unprivileged real time tasks and hard/soft
per task CPU rate caps.

The required scheduler can be selected at boot time by supplying a
string of the form "cpusched=<name>" where <name> is one of the names
listed above.

The default scheduler (that will be used in the absence of a "cpusched"
boot argument) can be configured at build time and is set to "ingosched"
by default.

The file /proc/scheduler contains a string describing the current scheduler.

The directory /sys/cpusched/<current scheduler name>/ contains any
scheduler configuration control files that may apply to the current
scheduler.

Peter
--
Peter Williams                                   pwil3...@bigpond.net.au

"Learning, n. The kind of ignorance distinguishing the studious."
  -- Ambrose Bierce
-
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/