The question then becomes what policy do we want to implement. In the current tool we can adjust PAGECACHE_MAX_BYTE (It defaults to 256KB, but I'd set it to more like 30MB).
However we may want a different sort of policy, e.g. cache reads but not writes. This would still reduce the pagecache usage by two thirds and would be very good on 1GB machines where filesystem.squashfs can easily fit in memory.
Actually, that could make it even easier, since there is already a tool to set POSIX_FADV_DONTNEED etc. via LD_PRELOAD.
I'll see if I can get userweb. kernel. org/~akpm/ pagecache- management/
http://
packaged and polished.
The question then becomes what policy do we want to implement. In the current tool we can adjust PAGECACHE_MAX_BYTE (It defaults to 256KB, but I'd set it to more like 30MB).
However we may want a different sort of policy, e.g. cache reads but not writes. This would still reduce the pagecache usage by two thirds and would be very good on 1GB machines where filesystem.squashfs can easily fit in memory.