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 from this list: send the line "unsubscribe linux-arch" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
