From: Christoph Lameter <cl@linux-foundation.org>
To: David Rientjes <rientjes@google.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
linux-mm@kvack.org, Tejun Heo <tj@kernel.org>
Subject: Re: [S+Q Cleanup 3/6] slub: Remove static kmem_cache_cpu array for boot
Date: Wed, 18 Aug 2010 09:54:36 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1008180953420.4025@router.home> (raw)
In-Reply-To: <alpine.DEB.2.00.1008171638160.31928@chino.kir.corp.google.com>
On Tue, 17 Aug 2010, David Rientjes wrote:
> On Tue, 17 Aug 2010, Christoph Lameter wrote:
>
> > Index: linux-2.6/mm/slub.c
> > ===================================================================
> > --- linux-2.6.orig/mm/slub.c 2010-08-13 10:32:45.000000000 -0500
> > +++ linux-2.6/mm/slub.c 2010-08-13 10:32:50.000000000 -0500
> > @@ -2062,23 +2062,14 @@ init_kmem_cache_node(struct kmem_cache_n
> > #endif
> > }
> >
> > -static DEFINE_PER_CPU(struct kmem_cache_cpu, kmalloc_percpu[KMALLOC_CACHES]);
> > -
> > static inline int alloc_kmem_cache_cpus(struct kmem_cache *s)
> > {
> > - if (s < kmalloc_caches + KMALLOC_CACHES && s >= kmalloc_caches)
> > - /*
> > - * Boot time creation of the kmalloc array. Use static per cpu data
> > - * since the per cpu allocator is not available yet.
> > - */
> > - s->cpu_slab = kmalloc_percpu + (s - kmalloc_caches);
> > - else
> > - s->cpu_slab = alloc_percpu(struct kmem_cache_cpu);
> > + BUILD_BUG_ON(PERCPU_DYNAMIC_EARLY_SIZE <
> > + SLUB_PAGE_SHIFT * sizeof(struct kmem_cache));
>
> This fails with CONFIG_NODES_SHIFT=10 on x86_64, which means it will fail
> the ia64 defconfig as well. struct kmem_cache stores nodemask pointers up
> to MAX_NUMNODES, which makes the conditional fail.
Hmmm... Wrong struct name. This needs to be struct kmem_cache_cpu not
struct kmem_cache. struct kmem_cache_cpu is sufficiently small.
--
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>
next prev parent reply other threads:[~2010-08-18 14:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 21:11 [S+Q Cleanup 0/6] SLUB: Cleanups Christoph Lameter
2010-08-17 21:11 ` [S+Q Cleanup 1/6] Slub: Force no inlining of debug functions Christoph Lameter
2010-08-17 23:13 ` David Rientjes
2010-08-17 21:11 ` [S+Q Cleanup 2/6] slub: remove dynamic dma slab allocation Christoph Lameter
2010-08-17 23:35 ` David Rientjes
2010-08-18 14:46 ` Christoph Lameter
2010-08-17 21:11 ` [S+Q Cleanup 3/6] slub: Remove static kmem_cache_cpu array for boot Christoph Lameter
2010-08-17 23:58 ` David Rientjes
2010-08-18 6:09 ` Tejun Heo
2010-08-18 14:54 ` Christoph Lameter [this message]
2010-08-17 21:11 ` [S+Q Cleanup 4/6] slub: Dynamically size kmalloc cache allocations Christoph Lameter
2010-08-17 21:11 ` [S+Q Cleanup 5/6] slub: Extract hooks for memory checkers from hotpaths Christoph Lameter
2010-08-18 0:28 ` David Rientjes
2010-08-18 14:58 ` Christoph Lameter
2010-08-17 21:11 ` [S+Q Cleanup 6/6] slub: Move gfpflag masking out of the hotpath Christoph Lameter
2010-08-18 0:35 ` David Rientjes
2010-08-18 15:46 ` Christoph Lameter
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.1008180953420.4025@router.home \
--to=cl@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=penberg@cs.helsinki.fi \
--cc=rientjes@google.com \
--cc=tj@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