Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 3 Dec 2018 08:20:23 +0900
From:   Minchan Kim <minchan@kernel.org>
To:     Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc:     Andrew Morton <akpm@linux-foundation.org>,
        LKML <linux-kernel@vger.kernel.org>,
        Joey Pabalinas <joeypabalinas@gmail.com>
Subject: Re: [PATCH v3 0/7] zram idle page writeback
Message-ID: <20181202232023.GB21560@google.com>
References: <20181127055429.251614-1-minchan@kernel.org>
 <20181130043656.GC605@jagdpanzerIV>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20181130043656.GC605@jagdpanzerIV>
User-Agent: Mutt/1.10.1+60 (6df12dc1) (2018-08-07)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, Nov 30, 2018 at 01:36:56PM +0900, Sergey Senozhatsky wrote:
> On (11/27/18 14:54), Minchan Kim wrote:
> > Inherently, swap device has many idle pages which are rare touched since
> > it was allocated. It is never problem if we use storage device as swap.
> > However, it's just waste for zram-swap.
> > 
> > This patchset supports zram idle page writeback feature.
> > 
> > * Admin can define what is idle page "no access since X time ago"
> > * Admin can define when zram should writeback them
> > * Admin can define when zram should stop writeback to prevent wearout
> > 
> > Detail is on each patch's description.
> > 
> > Below first two patches are -stable material so it could go first
> > separately with others in this series.
> 
> I had some time to look at the patches
> Reviewed-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> 
> Will give it some testing later; next week maybe.

Thanks Sergey!