From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752805Ab0HYI5o (ORCPT ); Wed, 25 Aug 2010 04:57:44 -0400 Received: from courier.cs.helsinki.fi ([128.214.9.1]:57923 "EHLO mail.cs.helsinki.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752747Ab0HYI5n (ORCPT ); Wed, 25 Aug 2010 04:57:43 -0400 Message-ID: <4C74DB05.7000101@cs.helsinki.fi> Date: Wed, 25 Aug 2010 11:57:41 +0300 From: Pekka Enberg User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: Tejun Heo CC: Christoph Lameter , Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: linux-next: build failure after merge of the final tree (slab tree related) References: <20100824120714.8918f8de.sfr@canb.auug.org.au> <4C740450.3030000@cs.helsinki.fi> <4C741029.7090300@cs.helsinki.fi> <4C74D1D7.4080608@kernel.org> In-Reply-To: <4C74D1D7.4080608@kernel.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 8/25/10 11:18 AM, Tejun Heo wrote: > Hello, > > On 08/24/2010 08:53 PM, Christoph Lameter wrote: >>> [ 0.000000] Kernel panic - not syncing: Cannot create slab kmem_cache >>> size=232 realsize=256 order=0 offset=0 flags=42000 >> >> alloc per cpu result in kmalloc which fails. >> >> Tejon: Is there some way we could get a reserved per cpu area under UP >> instead of fallback to slab allocations during bootup? > > Eh... nasty. Maybe we can create a alloc_percpu_early() function > which doesn't allow freeing of allocate memory and just redirect to > bootmem on UP? Yeah, I was thinking about that too. Pekka