With some further experimentation, I discovered this:
If I do not munmap() portions of the file already "read", but just
leave them pinned in RAM, the mmap/mlock performance is just as
fast as with read(2). OTOH, the size of the process grows dramatically
until it can't successfully mlock any more data.
So it appears that the process of truncating/splitting mapped regions
does something horrible to subsequent mlock behaviour. Any ideas what ?
--p
-
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:13 EST