From: Con Kolivas <kernel@kolivas.org>
To: Theodore Tso <tytso@mit.edu>
Cc: Ingo Molnar <mingo@elte.hu>, Mike Galbraith <efault@gmx.de>,
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: Tue, 13 Mar 2007 05:09:45 +1100 [thread overview]
Message-ID: <200703130509.45405.kernel@kolivas.org> (raw)
In-Reply-To: <20070312134806.GE4372@thunk.org>
On Tuesday 13 March 2007 00:48, Theodore Tso wrote:
> On Mon, Mar 12, 2007 at 10:23:06PM +1100, Con Kolivas wrote:
> > > > > We are getting good interactive response with a fair scheduler yet
> > > > > you seem intent on overloading it to find fault with it.
> > > >
> > > > I'm not trying to find fault, I'm TESTING AND REPORTING. Was.
> > >
> > > Con, could you please take Mike's report of this regression seriously
> > > and address it? Thanks,
> >
> > Sure.
> >
> > Mike the cpu is being proportioned out perfectly according to fairness as
> > I mentioned in the prior email, yet X is getting the lower latency
> > scheduling. I'm not sure within the bounds of fairness what more would
> > you have happen to your liking with this test case?
>
> Con,
>
> I think what we're discovering is that a "fair scheduler" is
> not going to cut it. After all, running X and ripping CD's and MP3
> encoding them is not exactly an esoteric use case. And like it or
> not, "nice" defaults to 4.
>
> I suspect Mike is right; the only way to deal with this
> regression is some scheduler hints from the desktop subsystem (i.e., X
> and friends). Yes, X is broken, it's horrible, yadda, yadda, yadda.
> It's also what everyone is using, and it's a fact of life. Just like
> we occasionally have had to work around ISA braindamage, and x86
> architecture braindamage, and ACPI braindamage all inflicted on us by
> Intel. This is just life, and sometimes the clean, elegant solution
> is not enough.
Instead of assuming it's bad, have you tried RSDL for yourself? Mike is using
2 lame threads for his test case.
--
-ck
next prev parent reply other threads:[~2007-03-12 18:10 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 [this message]
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
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=200703130509.45405.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@linux-foundation.org \
--cc=ck@vds.kolivas.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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).