Diego SANTA CRUZ wrote: > > Is the patch you mention the one at > http://www.uwsg.iu.edu/hypermail/linux/kernel/0201.0/1654.html ? > > How stable is it, there was not much debate on l-k about it. Is it a > good sign? > > Is that merged in any of the latest kernels? There are a few things you can do: You'll want http://www.zip.com.au/~akpm/linux/patches/2.4/2.4.18-rc1/make_request.patch to fix the elevator starvation problem. This is officially in 2.4.19-pre1. You'll want http://www.zip.com.au/~akpm/linux/patches/2.4/2.4.18-pre9/read-latency2.patch which promotes reads ahead of writes. Dunno if this will ever be merged, frankly. It's a *fundamental* change to what is probably the single most important pieve of code in the kernel, from a performance point of view. Now that's all well and good. With these patches, reads should proceed nicely. But if the process which is trying to read things accidentally does a write, it'll end up at the back of the queue, delayed for a long time. You shuld prevent such accidents by mounting your filesystems with the `noatime' option.
