I meant the page aging that occurs in vmscan.c, where we
decide on which page to unmap from a program's address
space. There we do aging while we don't age pages from
files that are read().
> > Now we can get severe problems with readahead when we
> > are evicting just read-in data because it isn't mapped,
>
> No, we don't. We don't evict just-read-in data, because we mark such
> pages as PG_Referenced. It takes two complete shrink_mmap() passes
> before we can evict such pages.
OK, I can (and have for quite a while) agree with this.
Kernels with this feature and enough memory will run great,
maybe small machines (<16M) will have a bit of trouble
keeping up readahead performance (since kswapd will have
made it's round a bit fast) but those machines will have
sucky performance anyway :)
Rik -- slowly getting used to dvorak kbd layout...
+-------------------------------------------------------------------+
| Linux memory management tour guide. H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+
-
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/