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 S932312AbcFCKYj (ORCPT <rfc822;w@1wt.eu>);
	Fri, 3 Jun 2016 06:24:39 -0400
Received: from mail-pf0-f193.google.com ([209.85.192.193]:34450 "EHLO
	mail-pf0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S932103AbcFCKYi (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 3 Jun 2016 06:24:38 -0400
Date: Fri, 3 Jun 2016 19:24:32 +0900
From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        linux-kernel@vger.kernel.org, linux-mm@kvack.org,
        Sangseok Lee <sangseok.lee@lge.com>, Chanho Min <chanho.min@lge.com>,
        Chan Gyun Jeong <chan.jeong@lge.com>
Subject: Re: [PATCH] mm: add NR_ZSMALLOC to vmstat
Message-ID: <20160603102432.GB586@swordfish>
References: <1464919731-13255-1-git-send-email-minchan@kernel.org>
 <20160603080141.GA490@swordfish>
 <20160603082336.GA18488@bbox>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160603082336.GA18488@bbox>
User-Agent: Mutt/1.6.1 (2016-04-27)
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/03/16 17:23), Minchan Kim wrote:
> On Fri, Jun 03, 2016 at 05:01:41PM +0900, Sergey Senozhatsky wrote:
> > On (06/03/16 11:08), Minchan Kim wrote:
> > > Now, zram is very popular for some of embedded world(e.g., TV, mobile
> > > phone). On those system, zsmalloc consumed memory size is never trivial
> > > (one of example from real product system, total memory: 800M, zsmalloc
> > > consumed: 150M), so we have used this out of tree patch to monitor system
> > > memory behavior via /proc/vmstat.
> > > 
> > > With zsmalloc in vmstat, it helps tracking down system behavior by
> > > memory usage.
> > 
> > Hello,
> > 
> > may be use zsmalloc stats file instead? as far as I know, you keep
> > zsmalloc stats enabled in production anyway.
> 
> It doesn't support per-zone stat which is important to show
> the fragmentation of the zone, for exmaple.

Ah, I see.

*just an idea*

may be zbud and z3fold folks will be interested as well, so may
be more generic name and define... um, my head doesn't work toay..
ZALLOC... ZPOOLALLOC... hm.. I think you got the idea.

	-ss