From: "T. J. Brumfield" <enderandrew@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Fwd: about modularization
Date: Fri, 3 Aug 2007 08:52:58 -0500 [thread overview]
Message-ID: <cdc89fe60708030652p634c6ea1y1f7b351f12a35a7a@mail.gmail.com> (raw)
In-Reply-To: <cdc89fe60708030651s54b5f0e0j938450632cf621c5@mail.gmail.com>
On 8/3/07, Ingo Molnar <mingo@elte.hu> wrote:
> snip...
Except that a working prototype of plugsched exists and functions
exactly as advertised. I understand that modules can be loaded and
unloaded, where as other aspects of the core kernel can't just
load/unload as the kernel is running, but the cpu scheduler could be
selected at boot via a command line, or as a kconfig option when
compiling like the io scheduler.
And while the io team may feel that it would be best to have one
scheduler that worked well under all circumstances, often this can't
simply be the case. Benchmarks over the years seem to suggest that
different schedulers work different for different situations. In that
regard, choice does seem to be nice.
CFS is apparently better in its simplicity, however others are
reporting that SD still provides benefits for 3D gaming. Perhaps
there are instances where even more schedulers like nicksched might be
the most appropriate solution.
-- T. J.
"In the beginning the Universe was created. This has made a lot of
people very angry and been widely regarded as a bad move."
--Douglas Adams
"Nihilism makes me smile."
--Christopher Quick
next prev parent reply other threads:[~2007-08-03 13:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 12:07 Scheduler Situation T. J. Brumfield
2007-08-03 12:31 ` Alistair John Strachan
2007-08-03 12:52 ` Oleksandr Natalenko
[not found] ` <192840a00708030616g22d9dd16o95b2620bfe3347a8@mail.gmail.com>
2007-08-03 13:27 ` Андрій Мішковський
2007-08-03 13:45 ` Alistair John Strachan
2007-08-03 13:00 ` debian developer
2007-08-03 15:28 ` about modularization Ingo Molnar
2007-08-03 13:19 ` Ingo Molnar
[not found] ` <cdc89fe60708030651s54b5f0e0j938450632cf621c5@mail.gmail.com>
2007-08-03 13:52 ` T. J. Brumfield [this message]
2007-08-03 15:02 ` Ingo Molnar
2007-08-03 15:13 ` Ingo Molnar
2007-08-03 17:47 ` Rene Herman
2007-08-03 18:59 ` Ingo Molnar
2007-09-01 22:02 ` Oleg Verych
[not found] ` <200708031354.15485.alistair@devzero.co.uk>
[not found] ` <cdc89fe60708030712q391de609o3999a870ea7cbcbd@mail.gmail.com>
[not found] ` <200708031540.29687.alistair@devzero.co.uk>
2007-08-03 14:51 ` Scheduler Situation T. J. Brumfield
2007-08-03 15:05 ` Alistair John Strachan
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=cdc89fe60708030652p634c6ea1y1f7b351f12a35a7a@mail.gmail.com \
--to=enderandrew@gmail.com \
--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®