From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762955AbXKMVkb (ORCPT ); Tue, 13 Nov 2007 16:40:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760109AbXKMVkX (ORCPT ); Tue, 13 Nov 2007 16:40:23 -0500 Received: from relay1.sgi.com ([192.48.171.29]:56927 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756631AbXKMVkV (ORCPT ); Tue, 13 Nov 2007 16:40:21 -0500 Date: Tue, 13 Nov 2007 13:40:19 -0800 (PST) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: David Miller cc: akpm@linux-foundation.org, linux-mm@vger.kernel.org, linux-kernel@vger.kernel.org, dada1@cosmosbay.com, schwidefsky@de.ibm.com Subject: Re: [patch 01/28] cpu alloc: The allocator In-Reply-To: <20071113.031510.151440585.davem@davemloft.net> Message-ID: References: <20071106195144.983665861@sgi.com> <20071106195157.878563669@sgi.com> <20071113.031510.151440585.davem@davemloft.net> 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 Tue, 13 Nov 2007, David Miller wrote: > One thing you could do is simply use a vmalloc allocation in the > non-virtualized case. Yuck. Meaning to add more crappy code. The bss limitations to 8M is a bit strange though. Do other platforms have the same issues?