Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936558AbXHMWKT (ORCPT ); Mon, 13 Aug 2007 18:10:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752922AbXHMWJ5 (ORCPT ); Mon, 13 Aug 2007 18:09:57 -0400 Received: from netops-testserver-3-out.sgi.com ([192.48.171.28]:51146 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751773AbXHMWJ4 (ORCPT ); Mon, 13 Aug 2007 18:09:56 -0400 Date: Mon, 13 Aug 2007 15:09:55 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Andi Kleen cc: Mel Gorman , Lee.Schermerhorn@hp.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH 3/4] Embed zone_id information within the zonelist->zones pointer In-Reply-To: <20070813225841.GG3406@bingen.suse.de> Message-ID: References: <20070809210616.14702.73376.sendpatchset@skynet.skynet.ie> <200708102013.49170.ak@suse.de> <200708110304.55433.ak@suse.de> <20070813225020.GE3406@bingen.suse.de> <20070813225841.GG3406@bingen.suse.de> 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 Content-Length: 1347 Lines: 38 On Tue, 14 Aug 2007, Andi Kleen wrote: > On Mon, Aug 13, 2007 at 03:00:14PM -0700, Christoph Lameter wrote: > > You said that ZONE_DMA will still be there right? So the zone will be > > There will be a (variable sized) dma zone, but not a ZONE_DMA entry in pgdat > or in the the fallback lists. Ahh.. Okay. > > > There are still other architectures that use it. Biggest offender > > > is s390. I'll leave them to their respective maintainers. > > > > IA64 also uses ZONE_DMA to support 32bit controllers. > > ZONE_DMA32 I thought? That one is not changed. x86_64 is the only platforms that uses ZONE_DMA32. Ia64 and other 64 bit platforms use ZONE_DMA for <4GB allocs. > > If so then it may be better to drop ZONE_DMA32 and make ZONE_DMA be below > > 4GB like other 64bit arches. > > That might be possible as a followup, but would change the driver > API. Is it worth it? It would leave the driver API as is for many arches. I think s/ZONE_DMA32/ZONE_DMA would restore the one DMA zone thing which is good. We could drop all ZONE_DMA32 stuff that is only needed by a single arch. - 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/