> Read-ahead (there is no write ahead) at mmap(2) is constrained
> to ONE instance per entire process memory space.
> That alone makes use of mmap(2) rather inefficient, doesn't it ?
That seems odd. Quite a few programs open a file multiple times and mmap
using different fd's to try and get multiple readaheads. I've never looked
to see if that works on Linux too
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Apr 07 2000 - 21:00:09 EST