Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757196AbYC1CaG (ORCPT ); Thu, 27 Mar 2008 22:30:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755069AbYC1C3z (ORCPT ); Thu, 27 Mar 2008 22:29:55 -0400 Received: from relay2.sgi.com ([192.48.171.30]:32879 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754737AbYC1C3y (ORCPT ); Thu, 27 Mar 2008 22:29:54 -0400 Date: Thu, 27 Mar 2008 19:27:50 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Jeremy Fitzhardinge cc: Ingo Molnar , LKML , Rusty Russell , KAMEZAWA Hiroyuki , Yasunori Goto , Dave Hansen , Andrew Morton Subject: Re: [PATCH 3 of 4] sparsemem: reduce i386 PAE section size In-Reply-To: <47EC574C.10006@goop.org> Message-ID: References: <47EC574C.10006@goop.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: 711 Lines: 19 On Thu, 27 Mar 2008, Jeremy Fitzhardinge wrote: > Christoph Lameter wrote: > > > > There are patches in mm which changes that situation. You should have 5 or 6 > > more flags to play with. > > > > Oh, good. We can play with it some more when everything gets merged together. Only works on i386 if you either use sparsemem / vmemmap or not sparsemem though. Is there any need for the other sparsemem memory models? Or could we disable them like on x86_64? -- 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/