From: "Thibaut VARENE" <T-Bone@parisc-linux.org>
To: "michael chang" <thenewme91@gmail.com>
Cc: "Con Kolivas" <kernel@kolivas.org>,
"ck list" <ck@vds.kolivas.org>,
"linux kernel mailing list" <linux-kernel@vger.kernel.org>
Subject: Re: [ck] Re: [PATCH][RSDL-mm 0/7] RSDL cpu scheduler for 2.6.21-rc3-mm2
Date: Tue, 13 Mar 2007 01:09:33 +0100 [thread overview]
Message-ID: <7d01f9f00703121709p66381704ic2dc10e90fdbf3d6@mail.gmail.com> (raw)
In-Reply-To: <b14e81f00703121438q6cdaffd0vdb08e0386961f057@mail.gmail.com>
On 3/12/07, michael chang <thenewme91@gmail.com> wrote:
> Considering the concepts put out by projects such as BOINC and
> SETI@Home, I wouldn't be thoroughly surprised by this ideology,
> although I do question the particular way this test case is being run.
If Con actually implements SCHED_IDLEPRIO in RSDL, life is good even
in that case.
> This seems to me like he's saying that there has to be a mechanism
> (outside of nice) that can be used to treat processes that "I" want to
> be interactive all special-like. It feels like something that would
> have been said in the design of what the scheduler was in -ck and is
> currently in vanilla.
Exactly. Driving us again toward the fact that different workloads
might benefit from different schedulers (eg: RSDL is cool for server
loads, previous staircase did an excellent job on desktop, etc) and
thus that having a choice of schedulers might be something that would
satisfy (some) people...
> To me, that fundamentally clashes with the design behind RSDL. That
> said, I could be wrong -- Con appears to have something that could be
> very promising up his sleeve that could come out sooner or later. Once
> he's written it, of course. In any case, RSDL seems very promising,
> for the most part.
It certainly is. "Negative" feedback can be a good thing too, as it
helps improving it anyway. It's nonetheless true that it's practically
impossible to satisfy 100% of use case with a single design, so
choices will have to be made.
HTH
T-Bone
--
Thibaut VARENE
http://www.parisc-linux.org/~varenet/
next prev parent reply other threads:[~2007-03-13 0:09 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 3:57 [PATCH][RSDL-mm 0/7] RSDL cpu scheduler for 2.6.21-rc3-mm2 Con Kolivas
2007-03-11 11:39 ` Mike Galbraith
2007-03-11 11:48 ` Con Kolivas
2007-03-11 12:08 ` Mike Galbraith
2007-03-11 12:10 ` Ingo Molnar
2007-03-11 12:20 ` Mike Galbraith
2007-03-11 21:18 ` Mike Galbraith
2007-03-12 7:22 ` Mike Galbraith
2007-03-12 7:48 ` Con Kolivas
2007-03-12 8:29 ` Con Kolivas
2007-03-12 8:55 ` Mike Galbraith
2007-03-12 9:22 ` Con Kolivas
2007-03-12 9:38 ` Mike Galbraith
2007-03-12 10:27 ` Con Kolivas
2007-03-12 10:57 ` Mike Galbraith
2007-03-12 11:08 ` Ingo Molnar
2007-03-12 11:23 ` Con Kolivas
2007-03-12 13:48 ` Theodore Tso
2007-03-12 18:09 ` Con Kolivas
2007-03-12 14:34 ` Mike Galbraith
2007-03-12 15:26 ` Linus Torvalds
2007-03-12 18:10 ` Con Kolivas
2007-03-12 19:36 ` Peter Zijlstra
2007-03-12 20:36 ` Mike Galbraith
2007-03-13 4:17 ` Kyle Moffett
2007-03-13 8:09 ` Ingo Molnar
2007-03-12 18:49 ` Con Kolivas
2007-03-12 19:06 ` Xavier Bestel
2007-03-13 17:21 ` Valdis.Kletnieks
2007-03-12 20:11 ` Mike Galbraith
2007-03-12 20:38 ` Con Kolivas
2007-03-12 20:45 ` Mike Galbraith
2007-03-12 22:51 ` Con Kolivas
2007-03-13 5:10 ` Mike Galbraith
2007-03-13 5:53 ` Con Kolivas
2007-03-13 6:08 ` [ck] " Rodney Gordon II
2007-03-13 6:17 ` Mike Galbraith
2007-03-13 7:53 ` Mike Galbraith
2007-03-13 8:22 ` Ingo Molnar
2007-03-13 8:18 ` Ingo Molnar
2007-03-13 8:22 ` Mike Galbraith
2007-03-13 9:21 ` Con Kolivas
2007-03-13 9:29 ` Ingo Molnar
2007-03-13 9:41 ` Con Kolivas
2007-03-13 10:50 ` Bill Huey
2007-03-13 9:31 ` [ck] " Con Kolivas
2007-03-13 10:24 ` Xavier Bestel
2007-03-13 23:19 ` Sanjoy Mahajan
2007-03-13 9:33 ` Mike Galbraith
2007-03-13 9:39 ` Ingo Molnar
2007-03-13 10:06 ` Con Kolivas
2007-03-13 11:23 ` Mike Galbraith
2007-03-13 11:41 ` Serge Belyshev
2007-03-13 11:46 ` Mike Galbraith
2007-03-13 15:36 ` John Stoffel
2007-03-13 14:17 ` Matt Mackall
2007-03-13 15:15 ` David Schwartz
2007-03-13 17:59 ` Jeremy Fitzhardinge
2007-03-13 19:58 ` David Schwartz
2007-03-13 20:10 ` Jeremy Fitzhardinge
2007-03-13 20:35 ` Bill Huey
2007-03-13 20:27 ` Bill Huey
2007-03-16 16:42 ` Pavel Machek
2007-03-12 23:43 ` David Lang
2007-03-13 2:23 ` Lee Revell
2007-03-13 6:00 ` David Lang
2007-03-12 21:34 ` [ck] " jos poortvliet
2007-03-12 21:38 ` michael chang
2007-03-13 0:09 ` Thibaut VARENE [this message]
2007-03-13 6:08 ` Mike Galbraith
2007-03-13 6:16 ` Con Kolivas
2007-03-13 6:30 ` Mike Galbraith
2007-03-12 20:42 ` Peter Zijlstra
2007-03-12 21:05 ` Serge Belyshev
2007-03-12 21:41 ` Mike Galbraith
2007-03-12 11:25 ` Mike Galbraith
2007-03-12 9:38 ` Xavier Bestel
2007-03-12 10:34 ` Con Kolivas
2007-03-12 16:38 ` Kasper Sandberg
2007-03-14 2:25 ` Valdis.Kletnieks
2007-03-14 3:25 ` Gabriel C
2007-03-14 9:44 ` Xavier Bestel
2007-03-12 8:44 ` Mike Galbraith
2007-03-11 14:32 ` Gene Heskett
2007-03-12 6:58 ` Radoslaw Szkodzinski
2007-03-12 11:16 ` Gene Heskett
2007-03-12 11:49 ` Gene Heskett
2007-03-12 11:58 ` Con Kolivas
2007-03-12 16:38 ` Gene Heskett
2007-03-12 18:34 ` Gene Heskett
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=7d01f9f00703121709p66381704ic2dc10e90fdbf3d6@mail.gmail.com \
--to=t-bone@parisc-linux.org \
--cc=ck@vds.kolivas.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thenewme91@gmail.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;
as well as URLs for NNTP newsgroup(s).