All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Dan Streetman <ddstreet@ieee.org>,
	Geliang Tang <geliangtang@gmail.com>,
	Nitin Gupta <ngupta@vflare.org>,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Linux-MM <linux-mm@kvack.org>, Vitaly Wool <vitalywool@gmail.com>
Subject: Re: [PATCH] zram: add zpool support
Date: Thu, 9 Jun 2016 10:43:45 +0900	[thread overview]
Message-ID: <20160609014345.GB655@swordfish> (raw)
In-Reply-To: <20160609013411.GA29779@bbox>

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@gmail.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

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

WARNING: multiple messages have this Message-ID (diff)
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Dan Streetman <ddstreet@ieee.org>,
	Geliang Tang <geliangtang@gmail.com>,
	Nitin Gupta <ngupta@vflare.org>,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Linux-MM <linux-mm@kvack.org>, Vitaly Wool <vitalywool@gmail.com>
Subject: Re: [PATCH] zram: add zpool support
Date: Thu, 9 Jun 2016 10:43:45 +0900	[thread overview]
Message-ID: <20160609014345.GB655@swordfish> (raw)
In-Reply-To: <20160609013411.GA29779@bbox>

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@gmail.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

  reply	other threads:[~2016-06-09  1:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08  9:39 [PATCH] zram: add zpool support Geliang Tang
2016-06-08  9:39 ` Geliang Tang
2016-06-08 14:51 ` Dan Streetman
2016-06-08 14:51   ` Dan Streetman
2016-06-09  1:34   ` Minchan Kim
2016-06-09  1:34     ` Minchan Kim
2016-06-09  1:43     ` Sergey Senozhatsky [this message]
2016-06-09  1:43       ` Sergey Senozhatsky
2016-06-13  9:11   ` Vitaly Wool
2016-06-13 20:04     ` Fwd: " Vitaly Wool
2016-06-15 14:42     ` [PATCH] zram: add zpool support v2 Geliang Tang
2016-06-15 14:42       ` Geliang Tang
2016-06-15 14:42       ` [PATCH] zram: update zram to use zpool Geliang Tang
2016-06-15 14:42         ` Geliang Tang
2016-06-15 14:54         ` Dan Streetman
2016-06-15 14:54           ` Dan Streetman
2016-06-15 15:33         ` kbuild test robot
2016-06-15 15:33           ` kbuild test robot
2016-06-15 23:17         ` Minchan Kim
2016-06-15 23:17           ` Minchan Kim
2016-06-17  8:30           ` Vitaly Wool
2016-06-17  8:30             ` Vitaly Wool
2016-06-17 12:28             ` Austin S. Hemmelgarn
2016-06-17 12:28               ` Austin S. Hemmelgarn
2016-06-20  8:00             ` Minchan Kim
2016-06-20  8:00               ` 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=20160609014345.GB655@swordfish \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=ddstreet@ieee.org \
    --cc=geliangtang@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=ngupta@vflare.org \
    --cc=vitalywool@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.