at
ly
As far as I understand it, RSDL always gives an equal share of cpu, but=20
interactive tasks can have lower latency, right? So you get in trouble with=
=20
interactive tasks only when their share isn't enough to actually do what th=
ey=20
have to do in that period, eg on a heavily (over?) loaded box. Staircase,=20
like mainline which gave them MORE than their share, would support that=20
(though this comes at a price).
So, if your box is overloaded to a great extend, X, which can use a lot of=
=20
cpu, can get unresponsive - unless it's negatively niced. But most other ap=
ps=20
aren't as demanding as X is, so they won't really suffer. Thus the problem =
is=20
mostly X. And at least part of that problem is being solved - X wasting cpu=
=20
cycles. Also, cpu's are getting stronger, and I think it's likely X's=20
relative CPU usage goes down as well.
In the long term, RSDL seems like the best way to go. Nice X down, and you =
got=20
most of the disadvantages. You still have the perfect fairness, no stalls a=
nd=20
starvation ;-)
If RSDL can be improved to help X, great. But introducing again the problem=
=20
which RSDL was supposed to solve would be pretty pointless. I think that's=
=20
what grumpy Con is trying to say, and he's right at it.
grtz
Jos
=2D-=20
Disclaimer:
Alles wat ik doe denk en zeg is gebaseerd op het wereldbeeld wat ik nu heb.=
=20
Ik ben niet verantwoordelijk voor wijzigingen van de wereld, of het beeld w=
at=20
ik daarvan heb, noch voor de daaruit voortvloeiende gedragingen van mezelf.=
=20
Alles wat ik zeg is aardig bedoeld, tenzij expliciet vermeld.