This version introduces a new scheduler, ingo_ll, which is a
modification of ingosched that uses average latencies to determine the
interactive bonuses awarded to tasks. In effect, tasks only receive
bonuses if they are necessary for the task to achieve satisfactory
latencies. For tasks waking from "interactive" sleeps their average
interactive latency is compared to a fixed limit and if it exceeds this
amount then their bonus is increased (if not it is compared to the same
limit divided by 2^8 and if it is smaller than this the bonus is
reduced). The limit may be set via the sysfs file
/sys/cpusched/ingo_ll/unacceptable_ia_latency. A similar process is
conducted for tasks waking from "non interactive" sleep except that the
limit is adjusted to take account of the number of tasks running on the
same CPU.
This version also continues the major gutting of the SPA based
schedulers to reduce overhead.
A patch for 2.6.16-rc2 is available at:
<http://prdownloads.sourceforge.net/cpuse/plugsched-6.3-for-2.6.16-rc2.patch?download>
and a patch for 2.6.16-rc2-mm1 is available at:
<http://prdownloads.sourceforge.net/cpuse/plugsched-6.3-for-2.6.16-rc2-mm1.patch?download>
Very Brief Documentation:
You can select a default scheduler at kernel build time. If you wish to
boot with a scheduler other than the default it can be selected at boot
time by adding:
cpusched=<scheduler>
to the boot command line where <scheduler> is one of: ingosched,
ingo_ll, nicksched, staircase, spa_no_frills, spa_ws, spa_svr, spa_ebs
or zaphod. If you don't change the default when you build the kernel
the default scheduler will be ingosched (which is the normal scheduler).
The scheduler in force on a running system can be determined by the
contents of:
/proc/scheduler
Control parameters for the scheduler can be read/set via files in:
/sys/cpusched/<scheduler>/
Peter
--
Peter Williams [email protected]
"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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
