From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 2 Aug 2007 14:26:21 +0100 From: Christoph Hellwig Subject: Re: [PATCH 3/4] vmemmap: pull out the vmemmap code into its own file Message-ID: <20070802132621.GA9511@infradead.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org Return-Path: To: Andy Whitcroft Cc: Andrew Morton , linux-mm@kvack.org, linux-arch@vger.kernel.org, Christoph Hellwig , Nick Piggin , Christoph Lameter , Mel Gorman List-ID: On Thu, Aug 02, 2007 at 10:25:35AM +0100, Andy Whitcroft wrote: > + * Special Kconfig settings: > + * > + * CONFIG_ARCH_POPULATES_SPARSEMEM_VMEMMAP > + * > + * The architecture has its own functions to populate the memory > + * map and provides a vmemmap_populate function. > + * > + * CONFIG_ARCH_POPULATES_SPARSEMEM_VMEMMAP_PMD > + * > + * The architecture provides functions to populate the pmd level > + * of the vmemmap mappings. Allowing mappings using large pages > + * where available. > + * > + * If neither are set then PAGE_SIZE mappings are generated which > + * require one PTE/TLB per PAGE_SIZE chunk of the virtual memory map. > + */ This is the kinda of mess I mean. Which architecturs set either of these and why? This code would be a lot more acceptable if we hadn't three different variants of the arch interface. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org