From: Bob Liu <bob.liu@oracle.com>
To: Mel Gorman <mgorman@suse.de>
Cc: Minchan Kim <minchan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jens Axboe <axboe@kernel.dk>,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
Nitin Gupta <ngupta@vflare.org>,
Konrad Rzeszutek Wilk <konrad@darnok.org>,
Luigi Semenzato <semenzato@google.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [PATCH v6 0/5] zram/zsmalloc promotion
Date: Fri, 16 Aug 2013 17:18:23 +0800 [thread overview]
Message-ID: <520DEE5F.70106@oracle.com> (raw)
In-Reply-To: <20130816091223.GF2296@suse.de>
Hi Mel,
On 08/16/2013 05:12 PM, Mel Gorman wrote:
> On Fri, Aug 16, 2013 at 09:33:47AM +0100, Mel Gorman wrote:
>> On Fri, Aug 16, 2013 at 01:26:41PM +0900, Minchan Kim wrote:
>> <SNIP>
>> It'll get even more entertaining if/when someone ever tries
>> to reimplement zcache although since Dan left I do not believe anyone is
>> planning to try.
>
> I should mention that Bob Liu did some work with zcache recently but is
> now looking like it'll be dropped from staging. I did not look at the
> details and I have no idea if anything else is planned with it.
>
The plan is like this:
Zcache dropped from staging.
As a result, for swap pages compression using zswap(zram).
For file pages compression using my new implemention of zcache(v3)
mm/zcache.c
If there is requirement we can merge zswap and zcachev3 in future!
--
Regards,
-Bob
next prev parent reply other threads:[~2013-08-16 9:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 5:55 [PATCH v6 0/5] zram/zsmalloc promotion Minchan Kim
2013-08-14 5:55 ` [PATCH v6 1/5] zsmalloc: add Kconfig for enabling page table method Minchan Kim
2013-08-14 5:55 ` [PATCH v6 2/5] zsmalloc: add more comment Minchan Kim
2013-08-14 5:55 ` [PATCH v6 3/5] zsmalloc: move it under zram Minchan Kim
2013-08-16 22:00 ` Seth Jennings
2013-08-20 4:21 ` Minchan Kim
2013-08-14 5:55 ` [PATCH v6 4/5] mm: export unmap_kernel_range Minchan Kim
2013-08-14 5:55 ` [PATCH v6 5/5] zram: promote zram from staging Minchan Kim
2013-08-14 15:53 ` [PATCH v6 0/5] zram/zsmalloc promotion Luigi Semenzato
2013-08-14 16:17 ` Minchan Kim
2013-08-15 0:18 ` Bob Liu
[not found] ` <520d883a.a2f6420a.6f36.0d66SMTPIN_ADDED_BROKEN@mx.google.com>
2013-08-16 4:35 ` Minchan Kim
2013-08-14 17:40 ` Mel Gorman
2013-08-14 18:15 ` Luigi Semenzato
2013-08-14 18:58 ` Minchan Kim
2013-08-15 17:12 ` Mel Gorman
2013-08-16 1:52 ` Bob Liu
2013-08-16 1:53 ` Bob Liu
2013-08-16 4:26 ` Minchan Kim
2013-08-16 4:55 ` Bob Liu
2013-08-16 8:33 ` Mel Gorman
2013-08-16 9:12 ` Mel Gorman
2013-08-16 9:18 ` Bob Liu [this message]
2013-08-16 12:49 ` Greg Kroah-Hartman
2013-08-16 9:12 ` Bob Liu
2013-08-19 3:18 ` Minchan Kim
2013-08-19 3:57 ` Bob Liu
2013-08-19 4:37 ` Minchan Kim
2013-08-19 5:29 ` Luigi Semenzato
2013-08-19 6:07 ` Bob Liu
2013-08-19 6:11 ` Minchan Kim
-- strict thread matches above, loose matches on Subject: below --
2013-08-14 5:51 Minchan Kim
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=520DEE5F.70106@oracle.com \
--to=bob.liu@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=konrad@darnok.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=penberg@cs.helsinki.fi \
--cc=semenzato@google.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;
as well as URLs for NNTP newsgroup(s).