linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Bob Liu <bob.liu@oracle.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Bob Liu <lliubbo@gmail.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	eternaleye@gmail.com, mgorman@suse.de,
	gregkh@linuxfoundation.org, akpm@linux-foundation.org,
	axboe@kernel.dk, sjenning@linux.vnet.ibm.com, ngupta@vflare.org,
	semenzato@google.com, penberg@iki.fi, sonnyrao@google.com,
	smbarber@google.com, konrad.wilk@oracle.com, riel@redhat.com,
	kmpark@infradead.org
Subject: Re: [PATCH 0/4] mm: merge zram into zswap
Date: Mon, 19 Aug 2013 12:32:07 +0800	[thread overview]
Message-ID: <52119FC7.5070406@oracle.com> (raw)
In-Reply-To: <20130819041044.GB26832@bbox>

Hi Minchan,

On 08/19/2013 12:10 PM, Minchan Kim wrote:
> On Sun, Aug 18, 2013 at 04:40:45PM +0800, Bob Liu wrote:
>> Both zswap and zram are used to compress anon pages in memory so as to reduce
>> swap io operation. The main different is that zswap uses zbud as its allocator
>> while zram uses zsmalloc. The other different is zram will create a block
>> device, the user need to mkswp and swapon it.
>>
>> Minchan has areadly try to promote zram/zsmalloc into drivers/block/, but it may
>> cause increase maintenance headaches. Since the purpose of zswap and zram are
>> the same, this patch series try to merge them together as Mel suggested.
>> Dropped zram from staging and extended zswap with the same feature as zram.
>>
>> zswap todo:
>> Improve the writeback of zswap pool pages!
>>
>> Bob Liu (4):
>>   drivers: staging: drop zram and zsmalloc
> 
> Bob, I feel you're very rude and I'm really upset.
> 
> You're just dropping the subsystem you didn't do anything without any consensus
> from who are contriubting lots of patches to make it works well for a long time.

I apologize for that, at least I should add [RFC] in the patch title!

-- 
Regards,
-Bob

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

      reply	other threads:[~2013-08-19  4:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-18  8:40 [PATCH 0/4] mm: merge zram into zswap Bob Liu
2013-08-18  8:40 ` [PATCH 1/4] drivers: staging: drop zram and zsmalloc Bob Liu
2013-08-18  8:40 ` [PATCH 2/4] mm: promote zsmalloc to mm/ Bob Liu
2013-08-18  8:40 ` [PATCH 3/4] mm: zswap: add supporting for zsmalloc Bob Liu
2013-08-19 16:59   ` Seth Jennings
2013-08-20  1:11     ` Bob Liu
2013-08-18  8:40 ` [PATCH 4/4] mm: zswap: create a pseudo device /dev/zram0 Bob Liu
2013-08-19 17:46   ` Seth Jennings
2013-08-20  2:03     ` Bob Liu
2013-08-19  4:10 ` [PATCH 0/4] mm: merge zram into zswap Minchan Kim
2013-08-19  4:32   ` Bob Liu [this message]

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=52119FC7.5070406@oracle.com \
    --to=bob.liu@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=eternaleye@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kmpark@infradead.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lliubbo@gmail.com \
    --cc=mgorman@suse.de \
    --cc=minchan@kernel.org \
    --cc=ngupta@vflare.org \
    --cc=penberg@iki.fi \
    --cc=riel@redhat.com \
    --cc=semenzato@google.com \
    --cc=sjenning@linux.vnet.ibm.com \
    --cc=smbarber@google.com \
    --cc=sonnyrao@google.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).