From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org
Subject: [LSF/MM TOPIC] [ATTEND] mm track: RAM utilization and page replacement topics
Date: Fri, 27 Jan 2012 09:19:44 -0800 (PST) [thread overview]
Message-ID: <f6fc422f-fbc2-4a19-b723-82c23f6aa3fe@default> (raw)
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?
Thanks,
Dan Magenheimer
"Mr. Tmem"
http://lwn.net/Articles/454795/
--
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>
next reply other threads:[~2012-01-27 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 17:19 Dan Magenheimer [this message]
2012-01-30 21:01 ` [LSF/MM TOPIC] [ATTEND] mm track: RAM utilization and page replacement topics Hugh Dickins
2012-02-01 14:03 ` Rik van Riel
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=f6fc422f-fbc2-4a19-b723-82c23f6aa3fe@default \
--to=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 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).