From: Peter Williams <pwil3058@bigpond.net.au>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ckrm-tech <ckrm-tech@lists.sourceforge.net>
Cc: Chris Han <xiphux@gmail.com>, Con Kolivas <kernel@kolivas.org>
Subject: [ANNOUNCE][RFC] PlugSched-3.0 meets CKRM-E17
Date: Wed, 09 Feb 2005 13:26:04 +1100 [thread overview]
Message-ID: <420974BC.7080600@bigpond.net.au> (raw)
A patch of PlugSched-3.0 against a 2.6.10 kernel with
ckrm-e17.2610.patch and cpu.ckrm-e17.v10.patch already applied is
available for download from:
<http://prdownloads.sourceforge.net/cpuse/plugsched-3.0%2Bckrm-E17-for-2.6.10.patch?download>
and a patchset and series file are available in at gzipped tarball at:
<http://prdownloads.sourceforge.net/cpuse/plugsched-3.0%2Bckrm-E17-for-2.6.10.patchset.tar.gz?download>
The model adopted in merging PlugSched with CKRM was to apply the CKRM
mechanisms as an optional adjunct to each of the schedulers (ingosched,
staircase, spa_no_frills and zaphod) which can be selected at boot time
by adding "cpusched=<scheduler name>" to the boot command line. If the
CKRM scheduler is included in the build then it can be
selected/deselected in the usual ways.
PlugSched's version number has been bumped to 3.0 as its interface has
been modified to increase the ability to share code between schedulers
as well as integrate with CKRM.
A stand alone version of PlugSched-3.0 will be available in a few days.
Peter
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
next reply other threads:[~2005-02-09 2:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 2:26 Peter Williams [this message]
2005-02-19 0:05 ` [ANNOUNCE][RFC] PlugSched-3.0 meets CKRM-E17 Peter Williams
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=420974BC.7080600@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--cc=ckrm-tech@lists.sourceforge.net \
--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