From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx191.postini.com [74.125.245.191]) by kanga.kvack.org (Postfix) with SMTP id 54D7B6B0008 for ; Wed, 6 Feb 2013 13:40:05 -0500 (EST) MIME-Version: 1.0 Message-ID: <73fe6782-21f4-47c5-886f-367374a3e600@default> Date: Wed, 6 Feb 2013 10:40:04 -0800 (PST) From: Dan Magenheimer Subject: RE: [LSF/MM TOPIC] In-kernel compression in the MM subsystem References: <601542b0-4c92-4d90-aed8-826235c06eab@default> <1360117134.2403.4.camel@kernel.cn.ibm.com> In-Reply-To: <1360117134.2403.4.camel@kernel.cn.ibm.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Sender: owner-linux-mm@kvack.org List-ID: To: Simon Jeons Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org, Seth Jennings , Nitin Gupta , Konrad Wilk , Minchan Kim > From: Simon Jeons [mailto:simon.jeons@gmail.com] > Subject: Re: [LSF/MM TOPIC] In-kernel compression in the MM subsystem >=20 > Hi Dan, > On Sat, 2013-01-26 at 12:16 -0800, Dan Magenheimer wrote: > > 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. > > >=20 > Is there benchmark to test each component in tmem? Hi Simon -- I'm not sure what you mean. Could you add a few words to clarify? Thanks, Dan -- 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: email@kvack.org