linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH v5 08/12] zsmalloc: introduce zspage structure
Date: Tue, 17 May 2016 10:14:18 +0900	[thread overview]
Message-ID: <20160517011418.GB31335@bbox> (raw)
In-Reply-To: <20160516030941.GD504@swordfish>

On Mon, May 16, 2016 at 12:09:41PM +0900, Sergey Senozhatsky wrote:
> 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?

Thanks, Will fix.

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

Hmm, of course, I can do it easily.
But zs_create_pool returns NULL without error propagation from sub
functions so I don't see any gain from returning errno from
create_cache. I don't mean I hate it but just need a justificaion
to persuade grumpy me.

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

Yeb.

> 
> [..]
> > +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 ..." ?

For source zspage, the policy is to find a fragment object from ZS_ALMOST_EMPTY.
For target zspage, the policy is to find a fragment object from ZS_ALMOST_FULL.

Do I misunderstand your question?

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

  reply	other threads:[~2016-05-17  1:14 UTC|newest]

Thread overview: 28+ 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 ` [PATCH v5 01/12] mm: use put_page to free page instead of putback_lru_page Minchan Kim
2016-05-09  2:20 ` [PATCH v5 02/12] mm: migrate: support non-lru movable page migration Minchan Kim
2016-05-16  7:04   ` Sergey Senozhatsky
2016-05-17  1:16     ` Minchan Kim
2016-05-16  7:17   ` Sergey Senozhatsky
2016-05-17  1:18     ` Minchan Kim
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-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 ` [PATCH v5 05/12] zsmalloc: use bit_spin_lock Minchan Kim
2016-05-16  1:17   ` Sergey Senozhatsky
2016-05-09  2:20 ` [PATCH v5 06/12] zsmalloc: use accessor Minchan Kim
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-16  2:14   ` Sergey Senozhatsky
2016-05-17  1:02     ` Minchan Kim
2016-05-09  2:20 ` [PATCH v5 08/12] zsmalloc: introduce zspage structure Minchan Kim
2016-05-16  3:09   ` Sergey Senozhatsky
2016-05-17  1:14     ` Minchan Kim [this message]
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-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 ` [PATCH v5 11/12] zsmalloc: page migration support Minchan Kim
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

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=20160517011418.GB31335@bbox \
    --to=minchan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sergey.senozhatsky.work@gmail.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 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).