From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762726AbXHOB4T (ORCPT ); Tue, 14 Aug 2007 21:56:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756307AbXHOB4I (ORCPT ); Tue, 14 Aug 2007 21:56:08 -0400 Received: from netops-testserver-4-out.sgi.com ([192.48.171.29]:49017 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754412AbXHOB4G (ORCPT ); Tue, 14 Aug 2007 21:56:06 -0400 Date: Tue, 14 Aug 2007 18:56:03 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Michael Ellerman cc: Lucio Correia , linux-kernel@vger.kernel.org, Arnd Bergmann Subject: Re: SLUB doesn't work with kdump kernel on Cell In-Reply-To: Message-ID: References: <1186604151.3608.46.camel@localhost.localdomain> <1187106239.3298.2.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 15 Aug 2007, Michael Ellerman wrote: > > Yes SLUB will fall back but not during bootstrap. Bootstrap needs to > > carefully place structures on the right nodes. We fail during bootstrap > > because there is *no* memory available on it. > > Sure, you want to have the structures on the right node if possible. > But seeing as there's no memory available, what is wrong with just > falling back? Then you have a useless kmem_cache_node structure that will never be used. What I could do is an alloc without GFP_THISNODE, check the location of the allocated memory and then print out a big fat warning that the memory setup is screwed up?