Messages in this thread |  | | Date | Tue, 27 Nov 2001 18:34:29 -0800 | From | Mike Fedyk <> | Subject | Re: Unresponiveness of 2.4.16 |
| |
On Tue, Nov 27, 2001 at 06:13:41PM -0800, Andrew Morton wrote: > Dieter N?tzel wrote: > > Don't forget to tune max-readahead. > > Yes. Readahead is fairly critical and there may be additional fixes > needed in this area. > > Someone recently added the /proc/sys/vm/max_readahead (?) tunable. > Beware of this. It only works for device drivers which do not > populate their own readhead table. For IDE, it *looks* like > it works, but it doesn't. For IDE, the only way to alter VM > readahead is via > > echo file_readahead:N > /proc/ide/ide0/hda/settings > > where N is in kilobytes in 2.4.16 kernels.
Any idea which drivers it will/won't work on? ie, "almost all ide" or "almost none of the ide driers"?
>In earlier kernels > it's kilopages (!).
Isn't this part of the max-readahead patch?
Does /proc/sys/vm/max_readahead affect scsi in any way?
What layer does /proc/sys/vm/max_readahead affect? Block? FS?
MF - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |