[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0703230907010.17666@sbz-30.cs.Helsinki.FI>
Date: Fri, 23 Mar 2007 09:09:00 +0200 (EET)
From: Pekka J Enberg <penberg@...helsinki.fi>
To: Eric Dumazet <dada1@...mosbay.com>
cc: akpm@...l.org, linux-kernel@...r.kernel.org, apw@...dowen.org,
hch@....de, manfred@...orfullife.com, christoph@...eter.com,
pj@....com
Subject: Re: [PATCH] slab: NUMA kmem_cache diet
(Please inline patches to the mail, makes it easier to review.)
On Thu, 22 Mar 2007, Eric Dumazet wrote:
> Some NUMA machines have a big MAX_NUMNODES (possibly 1024), but fewer possible
> nodes. This patch dynamically sizes the 'struct kmem_cache' to allocate only
> needed space.
>
> I moved nodelists[] field at the end of struct kmem_cache, and use the
> following computation in kmem_cache_init()
Hmm, what seems bit worrying is:
diff --git a/mm/slab.c b/mm/slab.c
index abf46ae..b187618 100644
--- a/mm/slab.c
+++ b/mm/slab.c
@@ -389,7 +389,6 @@ struct kmem_cache {
unsigned int buffer_size;
u32 reciprocal_buffer_size;
/* 3) touched by every alloc & free from the backend */
- struct kmem_list3 *nodelists[MAX_NUMNODES];
I think nodelists is placed at the beginning of the struct for a reason.
But I have no idea if it actually makes any difference...
Pekka
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists