Sorry for being late here.
I wanted to propose some further discussion on the volatile ranges concept.
Basically trying to sort out a coherent story around:
* My attempts at volatile ranges for shared tmpfs files (similar
functionality as Android's ashmem provides)
* Minchan's volatile ranges for anonymous memory
* How to track page volatility & purged state (via VMAs vs file
address_space)
* Purged data semantics (ie: Mozilla's request for SIGBUS on purged data
access vs zero fill)
* Aging anonymous pages in swapless systems
thanks
-john
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>