From: Gunter Fritz <gunter_fritz@gmx.de>
To: linux-kernel@vger.kernel.org
Cc: pwil3058@bigpond.net.au,
Christian Ege <christian.ege@cybertux.de>,
Christian Binkert <cbinkert@fh-konstanz.de>,
dkling@fh-konstanz.de, mbucher@fh-konstanz.de,
maechtel@fh-konstanz.de
Subject: scheduler switch at runtime
Date: Thu, 02 Mar 2006 22:41:37 +0100 [thread overview]
Message-ID: <1141335697.4419.15.camel@linux.site> (raw)
Hey
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 by Christian Ege 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
The dynsched project started as a part of our computer science study at
the university of applied sciences Konstanz. I hope it doesn't end with
our graduation. Thanks to Prof. Dr. Michael Mächtel, Peter Williams, who
provided us with helpful informations. The following people are
currently working with me on the dynsched project: Christian Ege, Dieter
Kling, Christian Binkert and Mathias Bucher.
Gunter Fritz
reply other threads:[~2006-03-02 21:03 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=1141335697.4419.15.camel@linux.site \
--to=gunter_fritz@gmx.de \
--cc=cbinkert@fh-konstanz.de \
--cc=christian.ege@cybertux.de \
--cc=dkling@fh-konstanz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maechtel@fh-konstanz.de \
--cc=mbucher@fh-konstanz.de \
--cc=pwil3058@bigpond.net.au \
/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