Re: [RFC v4 0/3] Support volatile for anonymous range

From: Arun Sharma
Date: Tue Dec 18 2012 - 13:52:56 EST


On 12/17/12 10:47 PM, Minchan Kim wrote:

I hope more inputs from user-space allocator people and test patch
with their allocator because it might need design change of arena
management for getting real vaule.

jemalloc knows how to handle MADV_FREE on platforms that support it. This looks similar (we'll need a SIGBUS handler that does the right thing = zero the page + mark it as non-volatile in the common case).

All of this of course assumes that apps madvise the kernel through APIs exposed by the malloc implementation - not via a raw syscall.

In other words, some new user space code needs to be written to test this out fully. Sounds feasible though.

-Arun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/