From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752374AbdF2JRO (ORCPT <rfc822;w@1wt.eu>);
        Thu, 29 Jun 2017 05:17:14 -0400
Received: from mail-pf0-f171.google.com ([209.85.192.171]:33300 "EHLO
        mail-pf0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751557AbdF2JRH (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 29 Jun 2017 05:17:07 -0400
Date: Thu, 29 Jun 2017 18:17:13 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        linux-kernel@vger.kernel.org, Juneho Choi <juno.choi@lge.com>,
        kernel-team <kernel-team@lge.com>
Subject: Re: [PATCH v1 0/7] writeback incompressible pages to storage
Message-ID: <20170629091713.GA392@jagdpanzerIV.localdomain>
References: <1498459987-24562-1-git-send-email-minchan@kernel.org>
 <20170628154157.GA528@tigerII.localdomain>
 <20170629084726.GB22335@bbox>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170629084726.GB22335@bbox>
User-Agent: Mutt/1.8.3 (2017-05-23)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hello,

On (06/29/17 17:47), Minchan Kim wrote:
[..]
> > > This patch supports writeback feature of zram so admin can set up
> > > a block device and with it, zram can save the memory via writing
> > > out the incompressile pages once it found it's incompressible pages
> > > (1/4 comp ratio) instead of keeping the page in memory.
> > 
> > hm, alternative idea. just an idea. can we try compressing the page
> > with another algorithm? example: downcast from lz4 to zlib? we can
> > set up a fallback "worst case" algorithm, so each entry can contain
> > additional flag that would tell if the src page was compressed with
> > the fast or slow algorithm. that sounds to me easier than "create a
> > new block device and bond it to zram, etc". but I may be wrong.
> 
> We tried it although it was static not dynamic adatation you suggested.

could you please explain more? I'm not sure I understand what
was the configuration (what is static adaptation?).

> However problem was media-stream data so zlib, lzam added just pointless
> overhead.

would that overhead be bigger than a full-blown I/O request to
another block device (potentially slow, or under load, etc. etc.)?

	-ss