From: "Randy.Dunlap" <rddunlap@osdl.org>
To: <piggin@cyberone.com.au>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Nick's scheduler policy
Date: Sun, 24 Aug 2003 20:27:37 -0700 (PDT) [thread overview]
Message-ID: <34251.4.4.25.4.1061782057.squirrel@www.osdl.org> (raw)
In-Reply-To: <3F48B12F.4070001@cyberone.com.au>
> Hi,
> Patch against 2.6.0-test4. It fixes a lot of problems here vs
> previous versions. There aren't really any open issues for me, so
> testers would be welcome.
>
...
>
> On the other hand, I expect the best cases and maybe most usual cases would
> be better on Con's... and Con might have since done some work in the latency
> area.
Has anyone developed a (run-time) scheduler [policy] selector, via
sysctl or sysfs, so that different kernel builds aren't required?
I know that I have heard discussions of this previously.
~Randy
next prev parent reply other threads:[~2003-08-25 3:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-24 12:35 [PATCH] Nick's scheduler policy Nick Piggin
2003-08-24 14:29 ` Felipe Alfaro Solana
2003-08-25 3:05 ` Nick Piggin
2003-08-25 22:30 ` Bill Davidsen
2003-08-24 16:55 ` Martin J. Bligh
2003-08-25 3:00 ` Nick Piggin
2003-08-25 10:41 ` [PATCH] Nick's scheduler policy v7 Nick Piggin
2003-08-25 11:03 ` Felipe Alfaro Solana
2003-08-25 14:36 ` Måns Rullgård
2003-08-26 3:24 ` Martin J. Bligh
2003-08-26 4:04 ` Nick Piggin
2003-08-26 9:44 ` Yaroslav Rastrigin
2003-08-27 9:28 ` Mike Galbraith
2003-08-25 3:27 ` Randy.Dunlap [this message]
2003-08-25 3:36 ` [PATCH] Nick's scheduler policy Nick Piggin
2003-08-26 3:16 ` Mike Fedyk
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=34251.4.4.25.4.1061782057.squirrel@www.osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.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;
as well as URLs for NNTP newsgroup(s).