On Tue, 23 Sep 2003, [iso-8859-1] emmanuel ALLAUD wrote:
> The problem with yielding is that you can have
> interactivity problem if the computer is loaded
> enough.
If you don't yield you have an interactivity problem.
What good is keeping your time slices if all you're doing
during them is busy waiting?
> At least that's what I have understood will
> happen with 2.6 linux kernels. The problem is to be
> able to tell the kernel : OK I know I have to wait so
> I give the CPU back, but I am an interactive process
> and I don't want my CPU back in 1 hour ;-) Perhaps
> there should be a "give my remaining slice time to
> someone else and then give me back the CPU" scheduler
> hint?
I'm not sure the 2.6 behavior sounds significantly worse
than the 2.4 behavior. I really don't understand what the
big deal is. I don't want the rest of my slice! I have nothing
to do with it except busy wait. Sure it would nice Linux
kernel didn't suck in this way, and I consider the sched_yield()
change a regression and a bug, but we make due with what we've
got and it's better than busy waiting.
Mark.
_______________________________________________
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
