[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.10.1403261042360.2057@nuc>
Date: Wed, 26 Mar 2014 10:43:37 -0500 (CDT)
From: Christoph Lameter <cl@...ux.com>
To: Sasha Levin <sasha.levin@...cle.com>
cc: Michal Hocko <mhocko@...e.cz>, Pekka Enberg <penberg@...nel.org>,
Matt Mackall <mpm@...enic.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: mm: slub: gpf in deactivate_slab
On Tue, 25 Mar 2014, Sasha Levin wrote:
> I'm not sure if there's anything special about this cache, codewise it's
> created as follows:
>
>
> inode_cachep = kmem_cache_create("inode_cache",
> sizeof(struct inode),
> 0,
> (SLAB_RECLAIM_ACCOUNT|SLAB_PANIC|
> SLAB_MEM_SPREAD),
> init_once);
>
>
> I'd be happy to dig up any other info required, I'm just not too sure
> what you mean by options for the cache?
Slab parameters can be change in /sys/kernel/slab/inode. Any debug
parameters active? More information about what was actually going on when
the gpf occured?
--
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