From: Christian Ege <christian.ege@cybertux.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: "Peter Williams" <pwil3058@bigpond.net.au>,
"Chris Han" <xiphux@gmail.com>,
"Con Kolivas" <kernel@kolivas.org>,
"William Lee Irwin III" <wli@holomorphy.com>,
"Jake Moilanen" <moilanen@austin.ibm.com>,
"Paolo Ornati" <ornati@fastwebnet.it>,
"Ingo Molnar" <mingo@elte.hu>,
"Michael Mächtel" <" maechtel"@fh-konstanz.de>,
"Dyn-Scheduler Mailingliste" <dyn-scheduler@cybertux.org>
Subject: [ANNOUNCE][RFC] dynsched-0.1.1 for 2.6.13
Date: Sun, 12 Mar 2006 18:11:41 +0100 [thread overview]
Message-ID: <1142183502.8725.8.camel@localhost.localdomain> (raw)
Hello,
there is a new version of dynsched released. It includes some minor
bugfixes and code cleanups. we are looking forward to your suggestions
and we are highly interested in a discussion.
In the next step we will port the patch to the current plugsched version
and split the patch in a plugsched part and a dynsched part.
The "dynsched" project aims switching the CPU scheduler at runtime. Its
based upon the "plugsched" patch by Peter Williams
(http://cpuse.sourceforge.net/). Increments to plugsched especially
a kthread, wich switchs between different schedulers, in sched.c and a
proc user interface.
Following scheduler implementations are currently supported:
* ingosched
* nicksched
* staircase
There are some missing functions like converting task_struct between the
schedulers. First tests on kernel 2.6.13.5 and 2.6.13.4
were successful. The spa based schedulers (such as spa_no_frills, zaphod
etc) are not yet supported. I hope they will be finished soon, just as
SMP support.
There is an alpha patch available at project site -
https://sourceforge.net/projects/dynsched
Using the procfs you can switch between the linux standard scheduler
(ingosched), nicksched and staircase schedulers by simply issuing:
echo "name_of_the_scheduler" > /proc/dynsched
There have been successful tests to switch the cpu scheduler while
running a fully loaded Linux system, running a KDE Desktop with a lot of
applications.
Christian Ege
--
------------------------------------------------------------------
Name: Christian Ege
mailto: christian.ege@cybertux.org
BLOG: http://chris.cybertux.org
WWW: http://www.cybertux.org
PGP Key fingerprint:
E436 3E5D CE47 7D0E DB63 F383 B41A 5FCF D4A1 D7A0
Informationen zu PGP: ( http://www.gnupg.de/ )
==================================================================
reply other threads:[~2006-03-12 17:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1142183502.8725.8.camel@localhost.localdomain \
--to=christian.ege@cybertux.de \
--cc=" maechtel"@fh-konstanz.de \
--cc=dyn-scheduler@cybertux.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=moilanen@austin.ibm.com \
--cc=ornati@fastwebnet.it \
--cc=pwil3058@bigpond.net.au \
--cc=wli@holomorphy.com \
--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
Powered by JetHome