From: John Stultz <john.stultz@linaro.org>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org
Subject: [LSF/MM TOPIC][ATTEND] Volatile Ranges
Date: Fri, 15 Feb 2013 13:03:24 -0800 [thread overview]
Message-ID: <511EA29C.3030301@linaro.org> (raw)
Sorry for being late here.
I wanted to propose some further discussion on the volatile ranges concept.
Basically trying to sort out a coherent story around:
* My attempts at volatile ranges for shared tmpfs files (similar
functionality as Android's ashmem provides)
* Minchan's volatile ranges for anonymous memory
* How to track page volatility & purged state (via VMAs vs file
address_space)
* Purged data semantics (ie: Mozilla's request for SIGBUS on purged data
access vs zero fill)
* Aging anonymous pages in swapless systems
thanks
-john
--
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>
next reply other threads:[~2013-02-15 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 21:03 John Stultz [this message]
2013-02-18 2:04 ` [LSF/MM TOPIC][ATTEND] Volatile Ranges 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=511EA29C.3030301@linaro.org \
--to=john.stultz@linaro.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).