From: Minchan Kim <minchan@kernel.org>
To: John Stultz <john.stultz@linaro.org>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org
Subject: Re: [LSF/MM TOPIC][ATTEND] Volatile Ranges
Date: Mon, 18 Feb 2013 11:04:29 +0900 [thread overview]
Message-ID: <20130218020429.GA7931@blaptop> (raw)
In-Reply-To: <511EA29C.3030301@linaro.org>
Hi John,
On Fri, Feb 15, 2013 at 01:03:24PM -0800, John Stultz wrote:
> 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
>
FYI,
I have a plan to redesign anon volatile range by some reasons.
In old version, I have been working with Jason who is jemalloc author
and he has a very interested in anon volatile.
I saw 2x faster with certain webserver workload with jemalloc which is
tweaked by Jason and me. Even, I have a plan to enhance it much higher.
If this topic is selected and I will be there,
I will share it with pleasure.
Thanks.
> * 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>
--
Kind regards,
Minchan Kim
--
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>
prev parent reply other threads:[~2013-02-18 2:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 21:03 [LSF/MM TOPIC][ATTEND] Volatile Ranges John Stultz
2013-02-18 2:04 ` Minchan Kim [this message]
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=20130218020429.GA7931@blaptop \
--to=minchan@kernel.org \
--cc=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 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.