linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <cl@linux-foundation.org>
To: Alex Chiang <achiang@hp.com>
Cc: penberg@cs.helsinki.fi, linux-ia64@vger.kernel.org, linux-mm@kvack.org
Subject: Re: SLUB ia64 linux-next crash bisected to 756dee75
Date: Thu, 14 Jan 2010 09:18:40 -0600 (CST)	[thread overview]
Message-ID: <alpine.DEB.2.00.1001140917110.14164@router.home> (raw)
In-Reply-To: <20100113002923.GF2985@ldl.fc.hp.com>

Try this


Subject: [SLUB] Size kmalloc_percpu correctly

We need kmalloc_percpu for all kmalloc caches not just for each shift
value.

Signed-off-by: Christoph Lameter <cl@linux-foundation.org>

---
 mm/slub.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: linux-2.6/mm/slub.c
===================================================================
--- linux-2.6.orig/mm/slub.c	2010-01-14 09:16:12.000000000 -0600
+++ linux-2.6/mm/slub.c	2010-01-14 09:16:27.000000000 -0600
@@ -2086,7 +2086,7 @@ init_kmem_cache_node(struct kmem_cache_n
 #endif
 }

-static DEFINE_PER_CPU(struct kmem_cache_cpu, kmalloc_percpu[SLUB_PAGE_SHIFT]);
+static DEFINE_PER_CPU(struct kmem_cache_cpu, kmalloc_percpu[KMALLOC_CACHES]);

 static inline int alloc_kmem_cache_cpus(struct kmem_cache *s, gfp_t flags)
 {

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

  parent reply	other threads:[~2010-01-14 15:18 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13  0:29 SLUB ia64 linux-next crash bisected to 756dee75 Alex Chiang
2010-01-13 14:59 ` Christoph Lameter
2010-01-14  0:53   ` Alex Chiang
2010-01-14 15:01     ` Christoph Lameter
2010-01-14 18:01       ` Alex Chiang
2010-01-14 15:18 ` Christoph Lameter [this message]
2010-01-14 18:22   ` Alex Chiang
2010-01-14 19:17     ` Pekka Enberg
2010-01-14 20:32       ` Alex Chiang
2010-01-14 20:58         ` Christoph Lameter
2010-01-14 21:29           ` Alex Chiang
2010-01-14 21:31             ` Pekka Enberg
2010-01-14 21:59               ` Christoph Lameter
2010-01-14 22:01             ` Christoph Lameter
2010-01-15 20:07 ` Christoph Lameter
2010-01-15 20:35   ` Lee Schermerhorn
2010-01-15 23:32     ` Christoph Lameter
2010-01-19 18:53       ` Christoph Lameter
2010-01-19 20:02         ` Alex Chiang
2010-01-19 20:29           ` Christoph Lameter
2010-01-19 21:29             ` Alex Chiang
2010-01-19 21:50               ` Christoph Lameter
2010-01-20 22:46                 ` Alex Chiang
2010-01-21 21:47                 ` Alex Chiang
2010-01-21 22:45                   ` Christoph Lameter
2010-01-21 23:05                     ` Alex Chiang
2010-01-21 23:43                       ` Christoph Lameter
2010-01-22  0:15                         ` Alex Chiang
2010-01-22 14:43                           ` Christoph Lameter
2010-01-22 16:37                             ` 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=alpine.DEB.2.00.1001140917110.14164@router.home \
    --to=cl@linux-foundation.org \
    --cc=achiang@hp.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penberg@cs.helsinki.fi \
    /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).