Jens Axboe wrote:
>
> ...
> > Anyway, lets wait for the numbers.
>
> It just 'feels' like the sort of change that might have odd side
> effects.
It's almost impossible to get READA to do anything. For example, in
current 2.5, if a READA attempt is actually aborted, end_buffer_io_sync
reports a "buffer I/O error". Every time. And nobody has reported this.
It _is_ possible to hit this in 2.5, because of ext2_preread_inode().
Probably, also it's possible to hit it in 2.4 with hundreds of processes
all issuing ext3 directory readahead. But it's pretty remote.
-
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/
This archive was generated by hypermail 2b29 : Wed Aug 07 2002 - 22:00:14 EST