From: Bob Liu <lliubbo@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org, sjenning@linux.vnet.ibm.com,
gregkh@linuxfoundation.org, ngupta@vflare.org,
minchan@kernel.org, konrad.wilk@oracle.com,
rcj@linux.vnet.ibm.com, mgorman@suse.de, riel@redhat.com,
penberg@kernel.org, akpm@linux-foundation.org,
Bob Liu <bob.liu@oracle.com>
Subject: [PATCH 0/2] zcache: a new start for upstream
Date: Sat, 20 Jul 2013 22:36:56 +0800 [thread overview]
Message-ID: <1374331018-11045-1-git-send-email-bob.liu@oracle.com> (raw)
We already have zswap helps reducing the swap out/in IO operations by
compressing anon pages.
It has been merged into v3.11-rc1 together with the zbud allocation layer.
However there is another kind of pages(clean file pages) suitable for
compression as well. Upstream has already merged its frontend(cleancache).
Now we are lacking of a backend of cleancache as zswap to frontswap.
Furthermore, we need to balance the number of compressed anon and file pages,
E.g. it's unfair to normal file pages if zswap pool occupies too much memory for
the storage of compressed anon pages.
Although the current version of zcache in staging tree has already done those
works mentioned above, the implementation is too complicated to be merged into
upstream.
What I'm looking for is a new way for zcache towards upstream.
The first change is no more staging tree.
Second is implemented a simple cleancache backend at first, which is based on
the zbud allocation same as zswap.
At the end, I hope we can combine the new cleancache backend with
zswap(frontswap backend), in order to have a generic in-kernel memory
compression solution in upstream.
Bob Liu (2):
zcache: staging: %s/ZCACHE/ZCACHE_OLD
mm: zcache: core functions added
drivers/staging/zcache/Kconfig | 12 +-
drivers/staging/zcache/Makefile | 4 +-
mm/Kconfig | 18 +
mm/Makefile | 1 +
mm/zcache.c | 840 +++++++++++++++++++++++++++++++++++++++
5 files changed, 867 insertions(+), 8 deletions(-)
create mode 100644 mm/zcache.c
--
1.7.10.4
next reply other threads:[~2013-07-20 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-20 14:36 Bob Liu [this message]
2013-07-20 14:36 ` [PATCH 1/2] zcache: staging: %s/ZCACHE/ZCACHE_OLD Bob Liu
2013-07-20 16:42 ` Greg KH
2013-07-20 14:36 ` [PATCH 2/2] mm: zcache: core functions added Bob Liu
[not found] ` <20130722150702.GB4706@variantweb.net>
2013-07-24 13:52 ` [PATCH 0/2] zcache: a new start for upstream Bob Liu
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=1374331018-11045-1-git-send-email-bob.liu@oracle.com \
--to=lliubbo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bob.liu@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=penberg@kernel.org \
--cc=rcj@linux.vnet.ibm.com \
--cc=riel@redhat.com \
--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
all inboxes | Powered by JetHome®