Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752621AbYCJROh (ORCPT ); Mon, 10 Mar 2008 13:14:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751107AbYCJRO1 (ORCPT ); Mon, 10 Mar 2008 13:14:27 -0400 Received: from relay1.sgi.com ([192.48.171.29]:37967 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751085AbYCJRO0 (ORCPT ); Mon, 10 Mar 2008 13:14:26 -0400 Date: Mon, 10 Mar 2008 10:13:49 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Andi Kleen cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH] [8/13] Enable the mask allocator for x86 In-Reply-To: <20080308115408.GC27074@one.firstfloor.org> Message-ID: References: <200803071007.493903088@firstfloor.org> <20080307090718.A609E1B419C@basil.firstfloor.org> <20080308115408.GC27074@one.firstfloor.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 943 Lines: 24 On Sat, 8 Mar 2008, Andi Kleen wrote: > What sparsemem reference do you mean? Its just the use of MAX_DMA_ADDRESS in mm/sparse-vmemmap.c > But the ZONE_DMA32 actually makes sense, but changing the semantics > under such a large driver base isn't a good idea. The driver base can only be the x86_64 only device drivers since the zone is not used by any other architectures. That is fairly small AFAICT. > It depends on the requirements of the bootmem user. Some do need > memory <4GB, some do not. The mask allocator itself is a client in fact > and it requires low memory of course. The point is that it would be good to relocate as much memory allocated at boot as possible beyond 4GB. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/