linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: lsf-pc@linuxfoundation.org
Cc: linux-mm@kvack.org
Subject: [LSF/MM TOPIC] improving in-kernel transcendent memory
Date: Fri, 4 Feb 2011 10:16:49 -0800 (PST)	[thread overview]
Message-ID: <85990ed5-f5d4-4ab2-809c-d181c865e86d@default> (raw)

The concepts of transcendent memory, including cleancache and frontswap,
have now graduated beyond virtualization to have real value in a
standalone kernel.  See the proposed kztmem patch:

http://lwn.net/Articles/423540/ 

For the page cache, this effectively extends the split LRU (active/inactive)
page queues to now include a new "queue" containing compressed clean page
cache pages.

For swap (as with ramzswap/zram), compressed in-memory swap pages may
negatively impact memory pressure in some workloads and a method
needs to be contrived to move these pages to a physical swap disk.

Some things to discuss:
1) What is the appropriate page count balance between the active queue,
   the inactive queue, and cleancache-compressed pages?
2) What triggers can be used for rebalancing?
3) Is there a better "source" for cleancache than pages reclaimed from
   the inactive queue?
4) Under what conditions should frontswap-compressed pages be "repatriated"
   to normal kernel memory (and possibly to disk)?

I also hope to also be able to describe and possibly demo a brand new in-kernel
(non-virtualization) user of transcendent memory (including both cleancache
and frontswap) that I think attendees in ALL tracks will find intriguing, but
I'm not ready to talk about until closer to LSF/MM workshop.  (Hopefully,
this will make a good lightning talk.)

Thanks,
Dan Magenheimer

--
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>

                 reply	other threads:[~2011-02-04 18:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=85990ed5-f5d4-4ab2-809c-d181c865e86d@default \
    --to=dan.magenheimer@oracle.com \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@linuxfoundation.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).