From: David Lang <david.lang@digitalinsight.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Con Kolivas <kernel@kolivas.org>, Ingo Molnar <mingo@elte.hu>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
ck list <ck@vds.kolivas.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH][RSDL-mm 0/7] RSDL cpu scheduler for 2.6.21-rc3-mm2
Date: Mon, 12 Mar 2007 15:43:36 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.63.0703121523220.1245@qynat.qvtvafvgr.pbz> (raw)
In-Reply-To: <1173732344.6431.54.camel@Homer.simpson.net>
On Mon, 12 Mar 2007, Mike Galbraith wrote:
> On Tue, 2007-03-13 at 07:38 +1100, Con Kolivas wrote:
>> On Tuesday 13 March 2007 07:11, Mike Galbraith wrote:
>>>
>>> Killing the known corner case starvation scenarios is wonderful, but
>>> let's not just pretend that interactive tasks don't have any special
>>> requirements.
>>
>> Now you're really making a stretch of things. Where on earth did I say that
>> interactive tasks don't have special requirements? It's a fundamental feature
>> of this scheduler that I go to great pains to get them as low latency as
>> possible and their fair share of cpu despite having a completely fair cpu
>> distribution.
>
> As soon as your cpu is fully utilized, fairness looses or interactivity
> loses. Pick one.
correct.
the problem is that it's hard (if not impossible) to properly identify what is
needed to make a system have good interactivity. in some cases it's a matter of
low latency (wake up a process as quickly as you can when whatever it was
waiting on is available), but in others it's a matter of allocating the _right_
process enough CPU (X needs enough CPU to do things)
where it's a matter of needing low-latency, it's possible to design a scheduler
that will do things in a predictable enough way that you know the max latency
you have to deal with (and the RSDL seems to do this)
the problem comes when this isn't enough. if you have several CPU hogs on a
system, and they are all around the same priority level, how can the scheduler
know which one needs the CPU the most for good interactivity?
in some cases you may be able to directly detect that your high-priority process
is waiting for another one (tracing pipes and local sockets for example), but
what if you are waiting for several of them? (think a multimedia desktop waiting
for the sound card, CDRom, hard drive, and video all at once) which one needs
the extra CPU the most?
Fairness is much easier to enforce (and much easier to understand)
the RSDL is concentrating on enforcing fairness, with bounded (and predictable)
latencies.
if you are willing to tell the system what you consider more important (and how
much more important you consider it), then it's much easier to figure out who to
give the CPU to. Con is just asking you to do this (and you already do, by doing
a nice -5. but it sounds like you want that to mean more then it currently does)
David Lang
next prev parent reply other threads:[~2007-03-13 0:07 UTC|newest]
Thread overview: 91+ 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 [this message]
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
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
2007-03-12 19:53 Al Boldi
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=Pine.LNX.4.63.0703121523220.1245@qynat.qvtvafvgr.pbz \
--to=david.lang@digitalinsight.com \
--cc=akpm@linux-foundation.org \
--cc=ck@vds.kolivas.org \
--cc=efault@gmx.de \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).