[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160609014345.GB655@swordfish>
Date: Thu, 9 Jun 2016 10:43:45 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To: Minchan Kim <minchan@...nel.org>
Cc: Dan Streetman <ddstreet@...e.org>,
Geliang Tang <geliangtang@...il.com>,
Nitin Gupta <ngupta@...are.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Linux-MM <linux-mm@...ck.org>, Vitaly Wool <vitalywool@...il.com>
Subject: Re: [PATCH] zram: add zpool support
Hello,
On (06/09/16 10:34), Minchan Kim wrote:
> On Wed, Jun 08, 2016 at 10:51:28AM -0400, Dan Streetman wrote:
> > On Wed, Jun 8, 2016 at 5:39 AM, Geliang Tang <geliangtang@...il.com> wrote:
> > > This patch adds zpool support for zram, it will allow us to use both
> > > the zpool api and directly zsmalloc api in zram.
> >
> > besides the problems below, this was discussed a while ago and I
> > believe Minchan is still against it, as nobody has so far shown what
> > the benefit to zram would be; zram doesn't need the predictability, or
> > evictability, of zbud or z3fold.
>
> Right.
>
> Geliang, I cannot ack without any *detail* that what's the problem of
> zram/zsmalloc, why we can't fix it in zsmalloc itself.
> The zbud and zsmalloc is otally different design to aim different goal
> determinism vs efficiency so you can choose what you want between zswap
> and zram rather than mixing the features.
I'd also probably Cc Vitaly Wool on this
(http://marc.info/?l=linux-mm&m=146537877415982&w=2)
-ss
Powered by blists - more mailing lists