> it seems unlikely that a process would make multiple system calls to mark many small regions of memory volatile.
Auto-freeing memory allocator? On call to free(), put in the linked list & mark volatile. If it's still there when you want it back, great. Otherwise, re-allocate.
Posted Nov 7, 2012 11:52 UTC (Wed) by juliank (subscriber, #45896)
[Link]
Most memory allocators don't do this on a page level though, but rather on a span of pages. Currently they use MADV_DONTNEED, but something that doesn't zero memory is more useful.
Many more words on volatile ranges
Posted Nov 7, 2012 12:54 UTC (Wed) by Trelane (subscriber, #56877)
[Link]