[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0705030936120.5165@blonde.wat.veritas.com>
Date: Thu, 3 May 2007 09:46:32 +0100 (BST)
From: Hugh Dickins <hugh@...itas.com>
To: Andrew Morton <akpm@...ux-foundation.org>
cc: Christoph Lameter <clameter@....com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: 2.6.22 -mm merge plans: slub
On Thu, 3 May 2007, Andrew Morton wrote:
> On Wed, 2 May 2007 10:25:47 -0700 (PDT) Christoph Lameter <clameter@....com> wrote:
>
> > +config ARCH_USES_SLAB_PAGE_STRUCT
> > + bool
> > + default y
> > + depends on SPLIT_PTLOCK_CPUS <= NR_CPUS
> > +
>
> That all seems to work as intended.
>
> However with NR_CPUS=8 SPLIT_PTLOCK_CPUS=4, enabling SLUB=y crashes the
> machine early in boot.
I thought that if that worked as intended, you wouldn't even
get the chance to choose SLUB=y? That was how it was working
for me (but I realize I didn't try more than make oldconfig).
>
> Too early for netconsole, no serial console. Wedges up uselessly with
> CONFIG_XMON=n, does mysterious repeated uncontrollable exceptions with
> CONFIG_XMON=y. This is all fairly typical for a powerpc/G5 crash :(
>
> However I was able to glimpse some stuff as it flew past. Crash started in
> flush_old_exec and ended in pgtable_free_tlb -> kmem_cache_free. I don't know
> how to do better than that I'm afraid, unless I'm to hunt down a PCIE serial
> card, perhaps.
That sounds like what happens when SLUB's pagestruct use meets
SPLIT_PTLOCK's pagestruct use. Does your .config really show
CONFIG_SLUB=y together with CONFIG_ARCH_USES_SLAB_PAGE_STRUCT=y?
Hugh
-
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