From: Arun Sharma <asharma@fb.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Michael Kerrisk <mtk.manpages@gmail.com>,
sanjay@google.com, Paul Turner <pjt@google.com>,
David Rientjes <rientjes@google.com>,
John Stultz <john.stultz@linaro.org>,
Christoph Lameter <cl@linux.com>,
Android Kernel Team <kernel-team@android.com>,
Robert Love <rlove@google.com>, Mel Gorman <mel@csn.ul.ie>,
Hugh Dickins <hughd@google.com>,
Dave Hansen <dave@linux.vnet.ibm.com>,
Rik van Riel <riel@redhat.com>,
Dave Chinner <david@fromorbit.com>, Neil Brown <neilb@suse.de>,
Mike Hommey <mh@glandium.org>, Taras Glek <tglek@mozilla.com>,
KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [RFC v4 0/3] Support volatile for anonymous range
Date: Tue, 18 Dec 2012 10:27:46 -0800 [thread overview]
Message-ID: <50D0B5A2.2010707@fb.com> (raw)
In-Reply-To: <1355813274-571-1-git-send-email-minchan@kernel.org>
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Arun Sharma <asharma@fb.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
Michael Kerrisk <mtk.manpages@gmail.com>, <sanjay@google.com>,
Paul Turner <pjt@google.com>,
David Rientjes <rientjes@google.com>,
John Stultz <john.stultz@linaro.org>,
Christoph Lameter <cl@linux.com>,
Android Kernel Team <kernel-team@android.com>,
Robert Love <rlove@google.com>, Mel Gorman <mel@csn.ul.ie>,
Hugh Dickins <hughd@google.com>,
Dave Hansen <dave@linux.vnet.ibm.com>,
Rik van Riel <riel@redhat.com>,
Dave Chinner <david@fromorbit.com>, Neil Brown <neilb@suse.de>,
Mike Hommey <mh@glandium.org>, Taras Glek <tglek@mozilla.com>,
KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [RFC v4 0/3] Support volatile for anonymous range
Date: Tue, 18 Dec 2012 10:27:46 -0800 [thread overview]
Message-ID: <50D0B5A2.2010707@fb.com> (raw)
In-Reply-To: <1355813274-571-1-git-send-email-minchan@kernel.org>
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
next prev parent reply other threads:[~2012-12-18 18:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 6:47 [RFC v4 0/3] Support volatile for anonymous range Minchan Kim
2012-12-18 6:47 ` Minchan Kim
2012-12-18 6:47 ` [RFC v4 1/3] Introduce new system call mvolatile Minchan Kim
2012-12-18 6:47 ` Minchan Kim
2012-12-18 6:47 ` [RFC v4 2/3] Discard volatile page Minchan Kim
2012-12-18 6:47 ` Minchan Kim
2012-12-18 6:47 ` [RFC v4 3/3] add PGVOLATILE vmstat count Minchan Kim
2012-12-18 6:47 ` Minchan Kim
2012-12-18 18:27 ` Arun Sharma [this message]
2012-12-18 18:27 ` [RFC v4 0/3] Support volatile for anonymous range Arun Sharma
2012-12-20 1:34 ` Minchan Kim
2012-12-20 1:34 ` Minchan Kim
2012-12-26 2:37 ` Kamezawa Hiroyuki
2012-12-26 2:37 ` Kamezawa Hiroyuki
2012-12-26 3:46 ` Minchan Kim
2012-12-26 3:46 ` Minchan Kim
2012-12-28 0:24 ` Kamezawa Hiroyuki
2012-12-28 0:24 ` Kamezawa Hiroyuki
2013-01-04 2:37 ` Minchan Kim
2013-01-04 2:37 ` Minchan Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50D0B5A2.2010707@fb.com \
--to=asharma@fb.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=dave@linux.vnet.ibm.com \
--cc=david@fromorbit.com \
--cc=hughd@google.com \
--cc=john.stultz@linaro.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kernel-team@android.com \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=mh@glandium.org \
--cc=minchan@kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=neilb@suse.de \
--cc=pjt@google.com \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=rlove@google.com \
--cc=sanjay@google.com \
--cc=tglek@mozilla.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.