Most of the time, you either have the IO overhead (and whether you use
read or mmap won't matter all that much, because you're IO limited), or
the thing is cached.
For gcc, it's cached 99% of the time, because most of the IO ends up being
header files (this is, of course, assuming that you're compiling a big
project, but if you're not, the big overhead is in loading _gcc_, not in
the pages it reads).
> Also read-with-PAGE_COPY has some really interesting implications for the
> page out routines. Because anytime you start the page out you have to
> copy the page. Not exactly when you want to increase the memory presure.
No no. Read my thing again. On swap-out, you just move the thing to the
Sure, that removes it from the regular cache, and that's possibly a
performance problem. But
> And not at all suitable for shared libraries.
No. Why would you "read" shared libraries? read is read, mmap is mmap. If
you want mmap, use mmap. Don't mess it up with MAP_COPY, which is not mmap
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/