It can probably be made writeable, within limits (caused by zones...)
But the interesting part is that 2.4 tries to estimate how much memory it
will need shortly (inactive_target) and try to keep that amount inactive
clean (inactive_clean) - clean inactive memory can be freed and reused very
quickly.
cat /proc/meminfo
My feeling is that, for now, keeping it untuneable can help us in finding
fixable cases...
/RogerL
-- Home page: http://www.norran.net/nra02596/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/