From: Minchan Kim <minchan@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Jens Axboe <axboe@kernel.dk>, Hugh Dickins <hughd@google.com>,
Rik van Riel <riel@redhat.com>,
Konrad Rzeszutek Wilk <konrad@darnok.org>,
Luigi Semenzato <semenzato@google.com>,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
Nitin Gupta <ngupta@vflare.org>, Bob Liu <bob.liu@oracle.com>,
Pekka Enberg <penberg@kernel.org>, Mel Gorman <mgorman@suse.de>
Subject: Re: [PATCH v9 0/4] zram/zsmalloc promotion
Date: Wed, 11 Dec 2013 11:09:59 +0900 [thread overview]
Message-ID: <20131211020959.GA17970@bbox> (raw)
In-Reply-To: <1386727479-18502-1-git-send-email-minchan@kernel.org>
Hello Greg,
On Wed, Dec 11, 2013 at 11:04:35AM +0900, Minchan Kim wrote:
> Zram is a simple pseudo block device which can keep data on
> in-memory with compressed[1].
>
> It have been used for many embedded system for several years
> One of significant usecase is in-memory swap device.
> Because NAND which is very popular on most embedded device
> is weak for frequent write without good wear-level
> and slow I/O hurts system's responsiblity so zram is really
> good choice to use memory efficiently.
>
> In previous trial, there was some argument[2] that zram has
> similar goal with zswap so let's merge zram's functionality
> into zswap via adding pseudo block device in zswap but I and
> some people(At least, Hugh and Rik) believe it's not a good idea.
> [2][3][4] and zswap might go writethrough model[5]. It makes
> clear difference zram and zswap.
>
> Zram itself is simple/well-designed/good abstraciton so it has
> clear market(ex, Android, TV, ChromeOS, some Linux distro) which
> is never niche. :)
>
> Another zram-blk's usecase is following as.
> The admin can use it as tmpfs so it could help small memory system.
> The tmpfs is never good solution for swapless embedded system.
>
> Patch 1 adds new Kconfig for zram to use page table method instead
> of copy.
>
> Patch 2 adds more comment for zsmalloc.
>
> Patch 3 moves zsmalloc under mm.
>
> Patch 4 moves zram from driver/staging to driver/blocks, finally.
Patch 1(suggested by Andrew Morton) and 2(Just comment to make review easy)
are prepartion for promotion so I hope it could be merged into your staging
regardless of allowing promotion at the moment.
Thanks.
--
Kind regards,
Minchan Kim
--
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 prev parent reply other threads:[~2013-12-11 2:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 2:04 [PATCH v9 0/4] zram/zsmalloc promotion Minchan Kim
2013-12-11 2:04 ` [PATCH v9 1/4] zsmalloc: add Kconfig for enabling page table method Minchan Kim
2013-12-11 2:04 ` [PATCH v9 2/4] zsmalloc: add more comment Minchan Kim
2013-12-11 2:04 ` [PATCH v9 3/4] zsmalloc: move it under mm Minchan Kim
2013-12-11 2:04 ` [PATCH v9 4/4] zram: promote zram from staging Minchan Kim
2013-12-11 2:09 ` Minchan Kim [this message]
2013-12-11 2:18 ` [PATCH v9 0/4] zram/zsmalloc promotion Greg Kroah-Hartman
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=20131211020959.GA17970@bbox \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bob.liu@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=hughd@google.com \
--cc=konrad@darnok.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=ngupta@vflare.org \
--cc=penberg@kernel.org \
--cc=riel@redhat.com \
--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).