On 04/02/2014 10:18 AM, Johannes Weiner wrote: > Hence my follow-up question in the other mail about how large we > expect such code caches to become in practice in relationship to > overall system memory. Are code caches interesting reclaim candidates > to begin with? Are they big enough to make the machine thrash/swap > otherwise?
A big chunk of the use cases here are for swapless systems anyway, so this is the *only* way for them to reclaim anonymous memory. Their choices are either to be constantly throwing away and rebuilding these objects, or to leave them in memory effectively pinned. In practice I did see ashmem (the Android thing that we're trying to replace) get used a lot by the Android web browser when I was playing with it. John said that it got used for storing decompressed copies of images. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
