Date: Sat, 25 Mar 2000 23:24:59 -0700
From: yodaiken@fsmlabs.com
The hidden assumption of the pre-emption patch is that there are kernel
paths that take more than 500us to reach a schedule or return to user
mode. Obviously there are such paths, but what are they and why can't they
be fixed?
Just to name a few obvious ones:
1) write(fd, buffer, SOME_LARGE_VALUE);
2) read(fd, buffer, SOME_LARGE_VALUE);
I honestly can't think of a way in which we'd want to deal with these
cases, except to perhaps check need_resched after or before copying
each page into/out-of the page cache out-of/into user space. And I
believe this is what the pre-emption patch and Ingo's low-latency
variant is up to basically.
Later,
David S. Miller
davem@redhat.com
-
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 : Fri Mar 31 2000 - 21:00:16 EST