[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f44c5fdf0703180022n44b2ca61o62602e54aaab3334@mail.gmail.com>
Date: Sun, 18 Mar 2007 08:22:02 +0100
From: "Radoslaw Szkodzinski" <astralstorm@...il.com>
To: "Mike Galbraith" <efault@....de>
Cc: "Kasper Sandberg" <lkml@...anurb.dk>,
"Al Boldi" <a1426z@...ab.com>,
"Andrew Morton" <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, ck@....kolivas.org,
"Linus Torvalds" <torvalds@...ux-foundation.org>,
"Nicholas Miell" <nmiell@...cast.net>
Subject: Re: [ck] Re: RSDL v0.31
On 3/18/07, Mike Galbraith <efault@....de> wrote:
> On Sun, 2007-03-18 at 07:47 +0100, Kasper Sandberg wrote:
>
> > > So neither does a good job with this load.
> > that sorely depends on what you mean by good job.
> >
> > It seems like what you call a good job is preserving the speed of the
> > gui(X + apps which uses it) at _ALL_ costs to other stuff.
>
> Wrong. I call a good job giving a _preference_ to the desktop. I call
> rigid fairness impractical for the desktop, and a denial of reality.
My sound programs (audacity, non-RT) and mplayer disaggree with you. :-)
Not to mention some more mundane stuff like Gajim. (no stall with its
slow PyGTK UI on RSDL)
(Hint: I'm using Xfce, not KDE)
I'd recon KDE regresses because of kioslaves waiting on a pipe
(communication with the app they're doing IO for) and then expiring.
That's why splitting IO from an app isn't exactly smart. It should at
least be ran in an another thread.
A much better approach would be running IO in the context of the app,
but using a common shared library.
Also, Beryl works better with RSDL too.
(blur doesn't "disable" itself sometimes - which is the result of a lag)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists