From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx179.postini.com [74.125.245.179]) by kanga.kvack.org (Postfix) with SMTP id D2D166B002B for ; Tue, 18 Dec 2012 13:28:31 -0500 (EST) Message-ID: <50D0B5A2.2010707@fb.com> Date: Tue, 18 Dec 2012 10:27:46 -0800 From: Arun Sharma MIME-Version: 1.0 Subject: Re: [RFC v4 0/3] Support volatile for anonymous range References: <1355813274-571-1-git-send-email-minchan@kernel.org> In-Reply-To: <1355813274-571-1-git-send-email-minchan@kernel.org> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Minchan Kim Cc: Andrew Morton , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Michael Kerrisk , sanjay@google.com, Paul Turner , David Rientjes , John Stultz , Christoph Lameter , Android Kernel Team , Robert Love , Mel Gorman , Hugh Dickins , Dave Hansen , Rik van Riel , Dave Chinner , Neil Brown , Mike Hommey , Taras Glek , KOSAKI Motohiro , KAMEZAWA Hiroyuki 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, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org