Hi all, Recently I was bitten badly by bad IO scheduler behavior on an important Linux server. An easy way to trigger this problem is to start a streaming write process: while : do dd if=/dev/zero of=foo bs=1M count=512 conv=notrunc done and then try doing a bunch of small reads: time (find kernel-tree -type f | xargs cat > /dev/null) With Linux 2.4.20, the reading takes a very long time to finish. I looked at backporting Jen's deadline scheduler to 2.4 but decided it would be too much work (especially for someone like me who doesn't know much about kernel hacking). I've come up with a fairly simple patch that seems to solve the starvation problem. Perhaps it is simple enough to get merged into the stable branch (after a little more polish). The basic idea is to give reads a boost if there are lots of write requests in the queue. I think my solution also prevents reads and writes from being starved indefinitely. Throughput also seems good although I have not done a lot of testing yet. I would greatly appreciate it if people could give it a test. Neil