From: Con Kolivas <kernel@kolivas.org>
To: Anupama Chandwani <anupama.chandwani@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Pavel Machek <pavel@ucw.cz>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Peter Williams <pwil3058@bigpond.net.au>,
William Lee Irwin III <wli@holomorphy.com>,
Alexander Nyberg <alexn@dsv.su.se>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: swappable scheduler in linux kernel
Date: Fri, 2 Sep 2005 00:23:21 +1000 [thread overview]
Message-ID: <200509020023.22485.kernel@kolivas.org> (raw)
In-Reply-To: <689eb34705090107196f3ef558@mail.gmail.com>
On Fri, 2 Sep 2005 00:19, Anupama Chandwani wrote:
> Hello,
> I am a final year coputre enginering student from Pune university,India.
> Im interested in linux kernel & saw the plugsched echanism, how its been
> made possible to change schedler policy at compile time.
>
> However, Im thinking of a scheduler that can dynamically change its policy
> or soe part of code for that matter hot swap with a copletely different
> scheduler at RUNTIME. something like IBM's K42. We can have scheduler modes
> like realtime or interactive which can be changed at runtime.
> Though its a pretty much completed problem to solve, there seem to be
> little commertial need of it.. can you suggest of its application or maybe
> your comments on this idea.
Runtime modification has possible uses in the form of hot scheduler upgrades
for systems in production for security upgrades or performance enhancements,
with virtually nil downtime. This was one of my ultimate aims when pushing
the original plugsched infrastructure. However both Linus and Ingo did not
like the plugsched idea at all thinking it would fragment work effort put
into the mainline scheduler and have lots of less good schedulers instead of
one scheduler to rule them all.
Cheers,
Con
parent reply other threads:[~2005-09-01 14:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <689eb34705090107196f3ef558@mail.gmail.com>]
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=200509020023.22485.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@osdl.org \
--cc=alexn@dsv.su.se \
--cc=anupama.chandwani@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=pavel@ucw.cz \
--cc=pwil3058@bigpond.net.au \
--cc=torvalds@osdl.org \
--cc=wli@holomorphy.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