From: Peter Williams <pwil3058@bigpond.net.au>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Con Kolivas <kernel@kolivas.org>, Chris Han <xiphux@gmail.com>
Subject: [ANNOUNCE][RFC] plugsched-2.0 patches ...
Date: Thu, 20 Jan 2005 12:23:25 +1100 [thread overview]
Message-ID: <41EF080D.7020101@bigpond.net.au> (raw)
... are now available from:
<http://prdownloads.sourceforge.net/cpuse/plugsched-2.0-for-2.6.10.patch?download>
as a single patch to linux-2.6.10 and at:
<http://prdownloads.sourceforge.net/cpuse/plugsched-2.0-for-2.6.10.patchset.tar.gz?download>
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 pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
next reply other threads:[~2005-01-20 1:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 1:23 Peter Williams [this message]
2005-01-20 1:58 ` [ANNOUNCE][RFC] plugsched-2.0 patches Kasper Sandberg
2005-01-20 16:14 ` Marc E. Fiuczynski
2005-01-20 17:51 ` Valdis.Kletnieks
2005-01-21 14:11 ` Jens Axboe
2005-01-21 16:29 ` Marc E. Fiuczynski
2005-01-21 16:43 ` Con Kolivas
2005-01-21 21:20 ` Peter Williams
2005-01-21 2:38 ` Peter Williams
2005-01-21 2:50 ` Marc E. Fiuczynski
2005-01-21 15:16 ` [ckrm-tech] " Shailabh Nagar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41EF080D.7020101@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiphux@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).