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
Date: Fri, 3 Jun 2016 19:24:32 +0900 [thread overview]
Message-ID: <20160603102432.GB586@swordfish> (raw)
In-Reply-To: <20160603082336.GA18488@bbox>
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
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-06-03 10:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 2:08 [PATCH] mm: add NR_ZSMALLOC to vmstat Minchan Kim
2016-06-03 8:01 ` Sergey Senozhatsky
2016-06-03 8:23 ` Minchan Kim
2016-06-03 10:24 ` Sergey Senozhatsky [this message]
2016-06-07 1:43 ` Minchan Kim
2016-06-09 1:40 ` Sergey Senozhatsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160603102432.GB586@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chan.jeong@lge.com \
--cc=chanho.min@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=sangseok.lee@lge.com \
--cc=sergey.senozhatsky.work@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).