[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0707101510410.5490@schroedinger.engr.sgi.com>
Date: Tue, 10 Jul 2007 15:12:38 -0700 (PDT)
From: Christoph Lameter <clameter@....com>
To: Matt Mackall <mpm@...enic.com>
cc: Pekka Enberg <penberg@...helsinki.fi>,
Nick Piggin <nickpiggin@...oo.com.au>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, suresh.b.siddha@...el.com,
corey.d.gough@...el.com, Denis Vlasenko <vda.linux@...glemail.com>,
Erik Andersen <andersen@...epoet.org>
Subject: Re: [patch 09/10] Remove the SLOB allocator for 2.6.23
On Tue, 10 Jul 2007, Matt Mackall wrote:
> following as the best MemFree numbers after several boots each:
>
> SLAB: 54796
> SLOB: 55044
> SLUB: 53944
> SLUB: 54788 (debug turned off)
That was without "slub_debug" as a parameter or with !CONFIG_SLUB_DEBUG?
Data size and code size will decrease if you compile with
!CONFIG_SLUB_DEBUG. slub_debug on the command line governs if debug
information is used.
> These numbers bounce around a lot more from boot to boot than I
> remember, so take these numbers with a grain of salt.
>
> Disabling the debug code in the build gives this, by the way:
>
> mm/slub.c: In function ÿÿinit_kmem_cache_nodeÿÿ:
> mm/slub.c:1873: error: ÿÿstruct kmem_cache_nodeÿÿ has no member named
> ÿÿfullÿÿ
A fix for that is in Andrew's tree.
Powered by blists - more mailing lists