From: Rik van Riel <riel@redhat.com>
To: John Stultz <john.stultz@linaro.org>
Cc: KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
Dave Hansen <dave@linux.vnet.ibm.com>,
Dmitry Adamushko <dmitry.adamushko@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Android Kernel Team <kernel-team@android.com>,
Robert Love <rlove@google.com>, Mel Gorman <mel@csn.ul.ie>,
Hugh Dickins <hughd@google.com>,
Dave Chinner <david@fromorbit.com>, Neil Brown <neilb@suse.de>,
Andrea Righi <andrea@betterlinux.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Taras Glek <tgek@mozilla.com>, Mike Hommey <mh@glandium.org>,
Jan Kara <jack@suse.cz>
Subject: Re: [PATCH 3/3] [RFC] tmpfs: Add FALLOC_FL_MARK_VOLATILE/UNMARK_VOLATILE handlers
Date: Sun, 10 Jun 2012 17:47:38 -0400 [thread overview]
Message-ID: <4FD515FA.2020708@redhat.com> (raw)
In-Reply-To: <4FD2C6C5.1070900@linaro.org>
On 06/08/2012 11:45 PM, John Stultz wrote:
> I *think* ideally, the pages in a volatile range should be similar to
> non-dirty file-backed pages. There is a cost to restore them, but
> freeing them is very cheap. The trick is that volatile ranges introduces
Easier to mark them dirty.
> a new relationship between pages. Since the neighboring virtual pages in
> a volatile range are in effect tied together, purging one effectively
> ruins the value of keeping the others, regardless of which zone they are
> physically.
Then the volatile ->writepage function can zap the whole
object.
--
All rights reversed
next prev parent reply other threads:[~2012-06-10 21:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 18:29 [PATCH 0/3] [RFC] Fallocate Volatile Ranges v2 John Stultz
2012-06-01 18:29 ` [PATCH 1/3] [RFC] Interval tree implementation John Stultz
2012-06-01 18:29 ` [PATCH 2/3] [RFC] Add volatile range management code John Stultz
2012-06-01 18:29 ` [PATCH 3/3] [RFC] tmpfs: Add FALLOC_FL_MARK_VOLATILE/UNMARK_VOLATILE handlers John Stultz
2012-06-01 20:17 ` KOSAKI Motohiro
2012-06-01 21:03 ` John Stultz
2012-06-01 21:37 ` KOSAKI Motohiro
2012-06-01 21:44 ` John Stultz
2012-06-01 22:34 ` KOSAKI Motohiro
2012-06-01 23:25 ` John Stultz
2012-06-06 19:52 ` KOSAKI Motohiro
2012-06-06 23:56 ` John Stultz
2012-06-07 10:55 ` Dmitry Adamushko
2012-06-07 23:41 ` Dave Hansen
2012-06-08 3:03 ` John Stultz
2012-06-08 4:50 ` KOSAKI Motohiro
2012-06-09 3:45 ` John Stultz
2012-06-10 6:35 ` Dmitry Adamushko
2012-06-10 21:47 ` Rik van Riel [this message]
2012-06-11 18:35 ` John Stultz
2012-06-12 1:21 ` John Stultz
2012-06-12 7:16 ` Minchan Kim
2012-06-12 16:03 ` KOSAKI Motohiro
2012-06-12 19:35 ` John Stultz
2012-06-13 0:10 ` Minchan Kim
2012-06-13 1:21 ` John Stultz
2012-06-13 4:42 ` Minchan Kim
2012-06-08 6:39 ` KOSAKI Motohiro
-- strict thread matches above, loose matches on Subject: below --
2012-06-01 23:38 [PATCH 0/3] [RFC] Fallocate Volatile Ranges v3 John Stultz
2012-06-01 23:38 ` [PATCH 3/3] [RFC] tmpfs: Add FALLOC_FL_MARK_VOLATILE/UNMARK_VOLATILE handlers John Stultz
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=4FD515FA.2020708@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andrea@betterlinux.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=dave@linux.vnet.ibm.com \
--cc=david@fromorbit.com \
--cc=dmitry.adamushko@gmail.com \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=john.stultz@linaro.org \
--cc=kernel-team@android.com \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=mh@glandium.org \
--cc=neilb@suse.de \
--cc=rlove@google.com \
--cc=tgek@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox