From: Rik van Riel <riel@redhat.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org
Subject: Re: [LSF/MM TOPIC] [ATTEND] mm track: RAM utilization and page replacement topics
Date: Wed, 01 Feb 2012 09:03:18 -0500 [thread overview]
Message-ID: <4F294626.4020207@redhat.com> (raw)
In-Reply-To: <f6fc422f-fbc2-4a19-b723-82c23f6aa3fe@default>
On 01/27/2012 12:19 PM, Dan Magenheimer wrote:
> Some (related) topics proposed for the MM track:
>
> 1) Optimizing the utilization of RAM as a resource, i.e. how do we teach the
> kernel to NOT use all RAM when it doesn't really "need" it. See
> http://lwn.net/Articles/475681/ (or if you don't want to read the whole
> article, start with "Interestingly, ..." four paragraphs from the end).
>
> 2) RAMster now exists and works... where are the holes and what next?
> http://marc.info/?l=linux-mm&m=132768187222840&w=2
>
> 3) Next steps in the page replacement algorithm:
> a) WasActive https://lkml.org/lkml/2012/1/25/300
> b) readahead http://marc.info/?l=linux-scsi&m=132750980203130
>
> 4) Remaining impediments for merging frontswap
>
> 5) Page flags and 64-bit-only... what are the tradeoffs?
I am interested in these topics.
--
All rights reversed
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-02-01 14:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 17:19 [LSF/MM TOPIC] [ATTEND] mm track: RAM utilization and page replacement topics Dan Magenheimer
2012-01-30 21:01 ` Hugh Dickins
2012-02-01 14:03 ` Rik van Riel [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=4F294626.4020207@redhat.com \
--to=riel@redhat.com \
--cc=dan.magenheimer@oracle.com \
--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.