linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wanpeng Li <liwanp@linux.vnet.ibm.com>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Pekka Enberg <penberg@kernel.org>,
	Christoph Lameter <cl@linux-foundation.org>,
	Matt Mackall <mpm@selenic.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slub: do not put a slab to cpu partial list when cpu_partial is 0
Date: Wed, 19 Jun 2013 16:00:32 +0800	[thread overview]
Message-ID: <20130619080032.GA31341@hacker.(null)> (raw)
In-Reply-To: <1371623635-26575-1-git-send-email-iamjoonsoo.kim@lge.com>

On Wed, Jun 19, 2013 at 03:33:55PM +0900, Joonsoo Kim wrote:
>In free path, we don't check number of cpu_partial, so one slab can
>be linked in cpu partial list even if cpu_partial is 0. To prevent this,
>we should check number of cpu_partial in put_cpu_partial().
>

How about skip get_partial entirely? put_cpu_partial is called 
in two paths, one is during refill cpu partial lists in alloc 
slow path, the other is in free slow path. And cpu_partial is 0 
just in debug mode. 

- alloc slow path, there is unnecessary to call get_partial 
  since cpu partial lists won't be used in debug mode. 
- free slow patch, new.inuse won't be true in debug mode 
  which lead to put_cpu_partial won't be called.

Regards,
Wanpeng Li 

>Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
>
>diff --git a/mm/slub.c b/mm/slub.c
>index 57707f0..7033b4f 100644
>--- a/mm/slub.c
>+++ b/mm/slub.c
>@@ -1955,6 +1955,9 @@ static void put_cpu_partial(struct kmem_cache *s, struct page *page, int drain)
> 	int pages;
> 	int pobjects;
>
>+	if (!s->cpu_partial)
>+		return;
>+
> 	do {
> 		pages = 0;
> 		pobjects = 0;
>-- 
>1.7.9.5
>
>--
>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>

--
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:[~2013-06-19  8:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19  6:33 [PATCH] slub: do not put a slab to cpu partial list when cpu_partial is 0 Joonsoo Kim
2013-06-19  8:00 ` Wanpeng Li [this message]
2013-06-19  8:00 ` Wanpeng Li
     [not found] ` <51c1652d.246e320a.4057.ffffed4fSMTPIN_ADDED_BROKEN@mx.google.com>
2013-06-19  8:52   ` Joonsoo Kim
2013-06-20  0:26     ` Wanpeng Li
2013-06-20  0:26     ` Wanpeng Li
     [not found]     ` <51c24c29.425c320a.433e.ffff9d8fSMTPIN_ADDED_BROKEN@mx.google.com>
2013-06-20  1:44       ` Joonsoo Kim
2013-06-20  2:32         ` Wanpeng Li
2013-06-20  2:32         ` Wanpeng Li
2013-06-19 14:25 ` Christoph Lameter
2013-07-07 15:47 ` Pekka Enberg

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='20130619080032.GA31341@hacker.(null)' \
    --to=liwanp@linux.vnet.ibm.com \
    --cc=cl@linux-foundation.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mpm@selenic.com \
    --cc=penberg@kernel.org \
    /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).