[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160603082336.GA18488@bbox>
Date: Fri, 3 Jun 2016 17:23:36 +0900
From: Minchan Kim <minchan@...nel.org>
To: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
CC: Andrew Morton <akpm@...ux-foundation.org>,
<linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>,
Sangseok Lee <sangseok.lee@....com>,
Chanho Min <chanho.min@....com>,
Chan Gyun Jeong <chan.jeong@....com>
Subject: Re: [PATCH] mm: add NR_ZSMALLOC to vmstat
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.
Powered by blists - more mailing lists