On Fri, 4 Feb 2000, Andrea Arcangeli wrote:
> >i've noticed and fixed these places long time ago in the lowlatency patch
> >series. There are a couple of other places that call uaccess.h functions
> >with ->state != RUNNING, and this was causing latency problems. (actually
> >i worked it around)
>
> You didn't worked it around IMHO. Setting the task as runnable before
> schedule() looks ok to me.
i believe it's a bug to set the task state and not call schedule
atomically within a short timeframe. (tty.c is such a case) So i think
those places which have this behavior should be fixed - and not the
functions which are called and might block should be hacked to set the
task state. I just chose the quick solution.
-- mingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Feb 07 2000 - 21:00:11 EST