From: Matthias Urlichs <smurf@smurf.noris.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][plugsched 0/28] Pluggable cpu scheduler framework
Date: Tue, 02 Nov 2004 22:28:33 +0100 [thread overview]
Message-ID: <pan.2004.11.02.21.28.32.869425@smurf.noris.de> (raw)
In-Reply-To: <20041101114124.GA31458@elte.hu>
Hi, Ingo Molnar wrote:
> I believe that by compartmenting in the wrong way [*] we kill the
> natural integration effects. We'd end up with 5 (or 20) bad generic
> schedulers that happen to work in one precise workload only, but there
> would not be enough push to build one good generic scheduler, because
> the people who are now forced to care about the Linux scheduler would be
> content about their specialized schedulers.
I don't think so. There are multiple attempts to build a better
generic scheduler (Con's for one), so there's your counterexample right
here. However, testing a different scheduler currently requires a kernel
recompile and a reboot.
I hate that. Ideally, the scheduler would be hotpluggable... but I can
live with a reboot. I don't think a kernel recompile to switch schedulers
makes sense, though, so I for one am likely not to bother. So far.
You can't actually develop a better scheduler if people need to go too
far out of their way to compare them.
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf@smurf.noris.de
next prev parent reply other threads:[~2004-11-02 21:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-30 14:32 Con Kolivas
2004-10-31 23:33 ` Pavel Machek
2004-10-31 23:37 ` Con Kolivas
2004-11-01 1:42 ` William Lee Irwin III
2004-11-01 11:41 ` Ingo Molnar
2004-11-01 13:08 ` Kasper Sandberg
2004-11-01 13:32 ` Con Kolivas
2004-11-01 14:23 ` Nick Piggin
2004-11-01 17:54 ` Jesse Barnes
2004-11-02 21:28 ` Matthias Urlichs [this message]
2004-11-02 22:30 ` Peter Chubb
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=pan.2004.11.02.21.28.32.869425@smurf.noris.de \
--to=smurf@smurf.noris.de \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®