Not all the time - when there is pressure to find more pages.
> Solaris keeps dirty pages after they have been flushed to their backing
> store, it's just when the system has to choose something to flush that it
> preferences filesystem over anonymous and executable, what's wrong with
Many of its pages are both file system and executable. Solaris shares
read-only pages between the caches and the mappings into process spaces.
I can understand favouring flushing mapped files because swap is
generally slower than restoring a file backed mapping
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/