Hi John, On Fri, Feb 15, 2013 at 01:03:24PM -0800, John Stultz wrote: > 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 > FYI, I have a plan to redesign anon volatile range by some reasons. In old version, I have been working with Jason who is jemalloc author and he has a very interested in anon volatile. I saw 2x faster with certain webserver workload with jemalloc which is tweaked by Jason and me. Even, I have a plan to enhance it much higher. If this topic is selected and I will be there, I will share it with pleasure. Thanks. > * 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> -- Kind regards, Minchan Kim -- 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>