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 S1752113AbeC0BDy (ORCPT <rfc822;w@1wt.eu>);
        Mon, 26 Mar 2018 21:03:54 -0400
Received: from mail-pl0-f66.google.com ([209.85.160.66]:33784 "EHLO
        mail-pl0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751903AbeC0BDx (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 26 Mar 2018 21:03:53 -0400
X-Google-Smtp-Source: AIpwx48MBmHYUbJ8Tm0n5e+Of2Hrdx/iGzVIDeQinVwfvIo3UwovKxwm7hF0l+hooWdSR9cwPLYGwA==
Date: Tue, 27 Mar 2018 10:03:47 +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>
Subject: Re: [PATCH 2/2] zram: idle memory tracking
Message-ID: <20180327010347.GA41148@rodete-desktop-imager.corp.google.com>
References: <20180326064951.123940-1-minchan@kernel.org>
 <20180326064951.123940-2-minchan@kernel.org>
 <20180327004911.GA467@jagdpanzerIV>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180327004911.GA467@jagdpanzerIV>
User-Agent: Mutt/1.9.2 (2017-12-15)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, Mar 27, 2018 at 09:49:11AM +0900, Sergey Senozhatsky wrote:
> On (03/26/18 15:49), Minchan Kim wrote:
> > zRam as swap is useful for small memory device. However, swap means
> > those pages on zram are mostly cold pages due to VM's LRU algorithm.
> > Especially, once init data for application are touched for launching,
> > they tend to be not accessed any more and finally swapped out.
> > zRAM can store such cold pages as compressed form but it's pointless
> > to keep in memory. Better idea is app developers free them directly
> > rather than remaining them on heap.
> > 
> > This patch tell us last accesss time of each block of zram via
> > "cat /sys/kernel/debug/zram/zram0/access_time".
> > 
> > The output is as follows,
> > 
> > 276 1250
> > 277 1800
> > ..  ..
> > ..  ..
> 
> So can we just use CONFIG_IDLE_PAGE_TRACKING + CONFIG_PAGE_OWNER?

The goal is not mapped memory tracking but one swapped out.
Can we do it by above two combination?

Furthermore, I am planning to provide incompressible pages as well
as access time so I will change interface at v2.

Thanks.