From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org, Seth Jennings <sjenning@linux.vnet.ibm.com>,
Nitin Gupta <ngupta@vflare.org>,
Konrad Wilk <konrad.wilk@oracle.com>,
Minchan Kim <minchan@kernel.org>
Subject: [LSF/MM TOPIC] In-kernel compression in the MM subsystem
Date: Sat, 26 Jan 2013 12:16:11 -0800 (PST) [thread overview]
Message-ID: <601542b0-4c92-4d90-aed8-826235c06eab@default> (raw)
There's lots of interesting things going on in kernel memory
management, but one only(?) increases the effective amount
of data that can be stored in a fixed amount of RAM: in-kernel
compression.
Since ramzswap/compcache (now zram) was first proposed in 2009
as an in-memory compressed swap device, there have been a number
of in-kernel compression solutions proposed, including
zcache, kztmem, and now zswap. Each shows promise to improve
performance by using compression under memory pressure to
reduce I/O due to swapping and/or paging. Each is still
in staging (though zram may be promoted by LSFMM 2013)
because each also brings a number of perplexing challenges.
I think it's time to start converging on which one or more
of these solutions, if any, should be properly promoted and
more fully integrated into the kernel memory management
subsystem. Before this can occur, it's important to build a
broader understanding and, hopefully, also a broader consensus
among the MM community on a number of key challenges and questions
in order to guide and drive further development and merging.
I would like to collect a list of issues/questions, and
start a discussion at LSF/MM by presenting this list, select
the most important, then lead a discussion on how ever many
there is time for. Most likely this is an MM-only discussion
though a subset might be suitable for a cross-talk presentataion.
Thanks!
Dan Magenheimer
LSF/MM attendee 2010,2011,2012
LSF/MM presenter (MM track) 2011,2012
--
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-01-26 20:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 20:16 Dan Magenheimer [this message]
2013-02-01 1:46 ` Simon Jeons
2013-02-06 2:18 ` Simon Jeons
2013-02-06 18:40 ` Dan Magenheimer
2013-02-13 8:08 ` Simon Jeons
2013-02-13 16:47 ` Dan Magenheimer
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=601542b0-4c92-4d90-aed8-826235c06eab@default \
--to=dan.magenheimer@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=sjenning@linux.vnet.ibm.com \
/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