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 S1752467AbcFCIXp (ORCPT <rfc822;w@1wt.eu>);
	Fri, 3 Jun 2016 04:23:45 -0400
Received: from LGEAMRELO13.lge.com ([156.147.23.53]:50955 "EHLO
	lgeamrelo13.lge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752189AbcFCIXm (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 3 Jun 2016 04:23:42 -0400
X-Original-SENDERIP: 156.147.1.127
X-Original-MAILFROM: minchan@kernel.org
X-Original-SENDERIP: 165.244.98.150
X-Original-MAILFROM: minchan@kernel.org
X-Original-SENDERIP: 10.177.223.161
X-Original-MAILFROM: minchan@kernel.org
Date: Fri, 3 Jun 2016 17:23:36 +0900
From: Minchan Kim <minchan@kernel.org>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
CC: 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: <20160603082336.GA18488@bbox>
References: <1464919731-13255-1-git-send-email-minchan@kernel.org>
 <20160603080141.GA490@swordfish>
MIME-Version: 1.0
In-Reply-To: <20160603080141.GA490@swordfish>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-MIMETrack: Itemize by SMTP Server on LGEKRMHUB03/LGE/LG Group(Release 8.5.3FP6|November
 21, 2013) at 2016/06/03 17:22:47,
	Serialize by Router on LGEKRMHUB03/LGE/LG Group(Release 8.5.3FP6|November
 21, 2013) at 2016/06/03 17:22:47,
	Serialize complete at 2016/06/03 17:22:47
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hello,

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.