All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	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: Thu, 9 Jun 2016 10:40:52 +0900	[thread overview]
Message-ID: <20160609014052.GA655@swordfish> (raw)
In-Reply-To: <20160607014340.GB26230@bbox>

Hello Minchan,

On (06/07/16 10:43), Minchan Kim wrote:
[..]
> > > 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
> 
> First motivation of stat came from fragmentation problem from zsmalloc
> which caused by storing many thin zpages in a pageframe and across two
> pageframes while zswap limits the limitation by design.
> 
> Second motivation is zsmalloc can allocate page from HIGH/movable zones
> so I want to know how distribution zsmalloced pages is.
> However, zbud doesn't.

good points.
well, my "motivation" was "on 64-bit systems high zone is empty,
so those are zones below the high zone that we are interested in".

[..]
> > be more generic name and define... um, my head doesn't work toay..
> > ZALLOC... ZPOOLALLOC... hm.. I think you got the idea.
> 
> Having said that, generic name is better rather than zsmalloc. Thanks.
> I want to use *zspage* which is term from the beginning of zprojects. :)

thanks!

	-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>

WARNING: multiple messages have this Message-ID (diff)
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	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: Thu, 9 Jun 2016 10:40:52 +0900	[thread overview]
Message-ID: <20160609014052.GA655@swordfish> (raw)
In-Reply-To: <20160607014340.GB26230@bbox>

Hello Minchan,

On (06/07/16 10:43), Minchan Kim wrote:
[..]
> > > 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
> 
> First motivation of stat came from fragmentation problem from zsmalloc
> which caused by storing many thin zpages in a pageframe and across two
> pageframes while zswap limits the limitation by design.
> 
> Second motivation is zsmalloc can allocate page from HIGH/movable zones
> so I want to know how distribution zsmalloced pages is.
> However, zbud doesn't.

good points.
well, my "motivation" was "on 64-bit systems high zone is empty,
so those are zones below the high zone that we are interested in".

[..]
> > be more generic name and define... um, my head doesn't work toay..
> > ZALLOC... ZPOOLALLOC... hm.. I think you got the idea.
> 
> Having said that, generic name is better rather than zsmalloc. Thanks.
> I want to use *zspage* which is term from the beginning of zprojects. :)

thanks!

	-ss

  reply	other threads:[~2016-06-09  1:40 UTC|newest]

Thread overview: 12+ 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  2:08 ` Minchan Kim
2016-06-03  8:01 ` Sergey Senozhatsky
2016-06-03  8:01   ` Sergey Senozhatsky
2016-06-03  8:23   ` Minchan Kim
2016-06-03  8:23     ` Minchan Kim
2016-06-03 10:24     ` Sergey Senozhatsky
2016-06-03 10:24       ` Sergey Senozhatsky
2016-06-07  1:43       ` Minchan Kim
2016-06-07  1:43         ` Minchan Kim
2016-06-09  1:40         ` Sergey Senozhatsky [this message]
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=20160609014052.GA655@swordfish \
    --to=sergey.senozhatsky.work@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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.