On Tue, 12 Sep 2000, Alan Cox wrote:
>> That problem: the original elevator code did not schedule I/O particularly
>> fairly under certain I/O usage patterns. So it got fixed.
>
>No it got hacked up a bit.
Why do you say it's not been fixed? Can you still reproduce hangs long as
a write(2) can write? I certainly can't.
>Actually my brain says that elapsed time based scheduling is the right thing
>to do. It certainly works for networks
Going in function of time it's a few liner patch with respect to the
current scheduler.
Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Sep 15 2000 - 21:00:18 EST