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: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH v5 08/12] zsmalloc: introduce zspage structure
Date: Mon, 16 May 2016 12:09:41 +0900	[thread overview]
Message-ID: <20160516030941.GD504@swordfish> (raw)
In-Reply-To: <1462760433-32357-9-git-send-email-minchan@kernel.org>

On (05/09/16 11:20), Minchan Kim wrote:
> We have squeezed meta data of zspage into first page's descriptor.
> So, to get meta data from subpage, we should get first page first
> of all. But it makes trouble to implment page migration feature
> of zsmalloc because any place where to get first page from subpage
> can be raced with first page migration. IOW, first page it got
> could be stale. For preventing it, I have tried several approahces
> but it made code complicated so finally, I concluded to separate
> metadata from first page. Of course, it consumes more memory. IOW,
> 16bytes per zspage on 32bit at the moment. It means we lost 1%
> at *worst case*(40B/4096B) which is not bad I think at the cost of
> maintenance.
> 
> Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> Signed-off-by: Minchan Kim <minchan@kernel.org>
[..]
> @@ -153,8 +138,6 @@
>  enum fullness_group {
>  	ZS_ALMOST_FULL,
>  	ZS_ALMOST_EMPTY,
> -	_ZS_NR_FULLNESS_GROUPS,
> -
>  	ZS_EMPTY,
>  	ZS_FULL
>  };
> @@ -203,7 +186,7 @@ static const int fullness_threshold_frac = 4;
>  
>  struct size_class {
>  	spinlock_t lock;
> -	struct page *fullness_list[_ZS_NR_FULLNESS_GROUPS];
> +	struct list_head fullness_list[2];

seems that it also has some cleaup bits in it.

[..]
> -static int create_handle_cache(struct zs_pool *pool)
> +static int create_cache(struct zs_pool *pool)
>  {
>  	pool->handle_cachep = kmem_cache_create("zs_handle", ZS_HANDLE_SIZE,
>  					0, 0, NULL);
> -	return pool->handle_cachep ? 0 : 1;
> +	if (!pool->handle_cachep)
> +		return 1;
> +
> +	pool->zspage_cachep = kmem_cache_create("zspage", sizeof(struct zspage),
> +					0, 0, NULL);
> +	if (!pool->zspage_cachep) {
> +		kmem_cache_destroy(pool->handle_cachep);
		^^^^^

do you need to NULL a pool->handle_cachep here?

zs_create_pool()
	if (create_cache() == 1) {
			pool->zspage_cachep NULL
			pool->handle_cachep !NULL   already freed -> kmem_cache_destroy()
			return 1;
		goto err
	}
err:
	zs_destroy_pool()
		destroy_cache() {
			kmem_cache_destroy(pool->handle_cachep);  !NULL and freed
			kmem_cache_destroy(pool->zspage_cachep);  NULL ok
		}


can we also switch create_cache() to errnos? I just like a bit
better
		return -ENOMEM;
	else
		return 0;

than

		return 1;
	else
		return 0;


> @@ -997,44 +951,38 @@ static void init_zspage(struct size_class *class, struct page *first_page)
>  		off %= PAGE_SIZE;
>  	}
>  
> -	set_freeobj(first_page, (unsigned long)location_to_obj(first_page, 0));
> +	set_freeobj(zspage,
> +		(unsigned long)location_to_obj(zspage->first_page, 0));

	static unsigned long location_to_obj()

it's already returning "(unsigned long)", so here and in several other places
this cast can be dropped.

[..]
> +static struct zspage *isolate_zspage(struct size_class *class, bool source)
>  {
> +	struct zspage *zspage;
> +	enum fullness_group fg[2] = {ZS_ALMOST_EMPTY, ZS_ALMOST_FULL};
> +	if (!source) {
> +		fg[0] = ZS_ALMOST_FULL;
> +		fg[1] = ZS_ALMOST_EMPTY;
> +	}
> +
> +	for (i = 0; i < 2; i++) {

sorry, why not "for (i = ZS_ALMOST_EMPTY; i <= ZS_ALMOST_FULL ..." ?

> +		zspage = list_first_entry_or_null(&class->fullness_list[fg[i]],
> +							struct zspage, list);
> +		if (zspage) {
> +			remove_zspage(class, zspage, fg[i]);
> +			return zspage;
>  		}
>  	}
>  
> -	return page;
> +	return zspage;
>  }

	-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: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH v5 08/12] zsmalloc: introduce zspage structure
Date: Mon, 16 May 2016 12:09:41 +0900	[thread overview]
Message-ID: <20160516030941.GD504@swordfish> (raw)
In-Reply-To: <1462760433-32357-9-git-send-email-minchan@kernel.org>

On (05/09/16 11:20), Minchan Kim wrote:
> We have squeezed meta data of zspage into first page's descriptor.
> So, to get meta data from subpage, we should get first page first
> of all. But it makes trouble to implment page migration feature
> of zsmalloc because any place where to get first page from subpage
> can be raced with first page migration. IOW, first page it got
> could be stale. For preventing it, I have tried several approahces
> but it made code complicated so finally, I concluded to separate
> metadata from first page. Of course, it consumes more memory. IOW,
> 16bytes per zspage on 32bit at the moment. It means we lost 1%
> at *worst case*(40B/4096B) which is not bad I think at the cost of
> maintenance.
> 
> Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> Signed-off-by: Minchan Kim <minchan@kernel.org>
[..]
> @@ -153,8 +138,6 @@
>  enum fullness_group {
>  	ZS_ALMOST_FULL,
>  	ZS_ALMOST_EMPTY,
> -	_ZS_NR_FULLNESS_GROUPS,
> -
>  	ZS_EMPTY,
>  	ZS_FULL
>  };
> @@ -203,7 +186,7 @@ static const int fullness_threshold_frac = 4;
>  
>  struct size_class {
>  	spinlock_t lock;
> -	struct page *fullness_list[_ZS_NR_FULLNESS_GROUPS];
> +	struct list_head fullness_list[2];

seems that it also has some cleaup bits in it.

[..]
> -static int create_handle_cache(struct zs_pool *pool)
> +static int create_cache(struct zs_pool *pool)
>  {
>  	pool->handle_cachep = kmem_cache_create("zs_handle", ZS_HANDLE_SIZE,
>  					0, 0, NULL);
> -	return pool->handle_cachep ? 0 : 1;
> +	if (!pool->handle_cachep)
> +		return 1;
> +
> +	pool->zspage_cachep = kmem_cache_create("zspage", sizeof(struct zspage),
> +					0, 0, NULL);
> +	if (!pool->zspage_cachep) {
> +		kmem_cache_destroy(pool->handle_cachep);
		^^^^^

do you need to NULL a pool->handle_cachep here?

zs_create_pool()
	if (create_cache() == 1) {
			pool->zspage_cachep NULL
			pool->handle_cachep !NULL   already freed -> kmem_cache_destroy()
			return 1;
		goto err
	}
err:
	zs_destroy_pool()
		destroy_cache() {
			kmem_cache_destroy(pool->handle_cachep);  !NULL and freed
			kmem_cache_destroy(pool->zspage_cachep);  NULL ok
		}


can we also switch create_cache() to errnos? I just like a bit
better
		return -ENOMEM;
	else
		return 0;

than

		return 1;
	else
		return 0;


> @@ -997,44 +951,38 @@ static void init_zspage(struct size_class *class, struct page *first_page)
>  		off %= PAGE_SIZE;
>  	}
>  
> -	set_freeobj(first_page, (unsigned long)location_to_obj(first_page, 0));
> +	set_freeobj(zspage,
> +		(unsigned long)location_to_obj(zspage->first_page, 0));

	static unsigned long location_to_obj()

it's already returning "(unsigned long)", so here and in several other places
this cast can be dropped.

[..]
> +static struct zspage *isolate_zspage(struct size_class *class, bool source)
>  {
> +	struct zspage *zspage;
> +	enum fullness_group fg[2] = {ZS_ALMOST_EMPTY, ZS_ALMOST_FULL};
> +	if (!source) {
> +		fg[0] = ZS_ALMOST_FULL;
> +		fg[1] = ZS_ALMOST_EMPTY;
> +	}
> +
> +	for (i = 0; i < 2; i++) {

sorry, why not "for (i = ZS_ALMOST_EMPTY; i <= ZS_ALMOST_FULL ..." ?

> +		zspage = list_first_entry_or_null(&class->fullness_list[fg[i]],
> +							struct zspage, list);
> +		if (zspage) {
> +			remove_zspage(class, zspage, fg[i]);
> +			return zspage;
>  		}
>  	}
>  
> -	return page;
> +	return zspage;
>  }

	-ss

  reply	other threads:[~2016-05-16  3:09 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09  2:20 [PATCH v5 00/13] Support non-lru page migration Minchan Kim
2016-05-09  2:20 ` Minchan Kim
2016-05-09  2:20 ` Minchan Kim
2016-05-09  2:20 ` [PATCH v5 01/12] mm: use put_page to free page instead of putback_lru_page Minchan Kim
2016-05-09  2:20   ` Minchan Kim
2016-05-09  2:20 ` [PATCH v5 02/12] mm: migrate: support non-lru movable page migration Minchan Kim
2016-05-09  2:20 ` Minchan Kim
2016-05-09  2:20   ` Minchan Kim
2016-05-09  2:20   ` Minchan Kim
2016-05-16  7:04   ` Sergey Senozhatsky
2016-05-16  7:04     ` Sergey Senozhatsky
2016-05-17  1:16     ` Minchan Kim
2016-05-17  1:16       ` Minchan Kim
2016-05-17  1:16     ` Minchan Kim
2016-05-16  7:04   ` Sergey Senozhatsky
2016-05-16  7:17   ` Sergey Senozhatsky
2016-05-16  7:17     ` Sergey Senozhatsky
2016-05-16  7:17     ` Sergey Senozhatsky
2016-05-17  1:18     ` Minchan Kim
2016-05-17  1:18       ` Minchan Kim
2016-05-17  1:18       ` Minchan Kim
2016-05-17  1:30       ` Sergey Senozhatsky
2016-05-17  1:30         ` Sergey Senozhatsky
2016-05-17  1:30       ` Sergey Senozhatsky
2016-05-09  2:20 ` [PATCH v5 03/12] mm: balloon: use general non-lru movable page feature Minchan Kim
2016-05-09  2:20   ` Minchan Kim
2016-05-09  2:20   ` Minchan Kim
2016-05-16 19:16   ` kbuild test robot
2016-05-16 19:16     ` kbuild test robot
2016-05-16 19:16     ` kbuild test robot
2016-05-09  2:20 ` [PATCH v5 04/12] zsmalloc: keep max_object in size_class Minchan Kim
2016-05-09  2:20   ` Minchan Kim
2016-05-09  2:20 ` [PATCH v5 05/12] zsmalloc: use bit_spin_lock Minchan Kim
2016-05-09  2:20   ` Minchan Kim
2016-05-16  1:17   ` Sergey Senozhatsky
2016-05-16  1:17     ` Sergey Senozhatsky
2016-05-09  2:20 ` [PATCH v5 06/12] zsmalloc: use accessor Minchan Kim
2016-05-09  2:20   ` Minchan Kim
2016-05-16  1:48   ` Sergey Senozhatsky
2016-05-16  1:48     ` Sergey Senozhatsky
2016-05-09  2:20 ` [PATCH v5 07/12] zsmalloc: factor page chain functionality out Minchan Kim
2016-05-09  2:20   ` Minchan Kim
2016-05-16  2:14   ` Sergey Senozhatsky
2016-05-16  2:14     ` Sergey Senozhatsky
2016-05-17  1:02     ` Minchan Kim
2016-05-17  1:02       ` Minchan Kim
2016-05-09  2:20 ` [PATCH v5 08/12] zsmalloc: introduce zspage structure Minchan Kim
2016-05-09  2:20   ` Minchan Kim
2016-05-16  3:09   ` Sergey Senozhatsky [this message]
2016-05-16  3:09     ` Sergey Senozhatsky
2016-05-17  1:14     ` Minchan Kim
2016-05-17  1:14       ` Minchan Kim
2016-05-17  1:27       ` Sergey Senozhatsky
2016-05-17  1:27         ` Sergey Senozhatsky
2016-05-09  2:20 ` [PATCH v5 09/12] zsmalloc: separate free_zspage from putback_zspage Minchan Kim
2016-05-09  2:20   ` Minchan Kim
2016-05-16  3:15   ` Sergey Senozhatsky
2016-05-16  3:15     ` Sergey Senozhatsky
2016-05-09  2:20 ` [PATCH v5 10/12] zsmalloc: use freeobj for index Minchan Kim
2016-05-09  2:20   ` Minchan Kim
2016-05-09  2:20 ` [PATCH v5 11/12] zsmalloc: page migration support Minchan Kim
2016-05-09  2:20   ` Minchan Kim
2016-05-16 19:33   ` kbuild test robot
2016-05-16 19:33     ` kbuild test robot
2016-05-09  2:20 ` [PATCH v5 12/12] zram: use __GFP_MOVABLE for memory allocation Minchan Kim
2016-05-09  2:20   ` Minchan Kim

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=20160516030941.GD504@swordfish \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --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.