On Fri, 13 Jul 2007 14:36:39 +0100 Andy Whitcroft <[EMAIL PROTECTED]> wrote:
> x86_64 uses 2M page table entries to map its 1-1 kernel space. > We also implement the virtual memmap using 2M page table entries. So > there is no additional runtime overhead over FLATMEM, initialisation > is slightly more complex. As FLATMEM still references memory to > obtain the mem_map pointer and SPARSEMEM_VMEMMAP uses a compile > time constant, SPARSEMEM_VMEMMAP should be superior. > > With this SPARSEMEM becomes the most efficient way of handling > virt_to_page, pfn_to_page and friends for UP, SMP and NUMA on x86_64. > > [EMAIL PROTECTED]: code resplit, style fixups] > From: Christoph Lameter <[EMAIL PROTECTED]> > Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]> > Signed-off-by: Andy Whitcroft <[EMAIL PROTECTED]> > Acked-by: Mel Gorman <[EMAIL PROTECTED]> > --- > diff --git a/Documentation/x86_64/mm.txt b/Documentation/x86_64/mm.txt Please put the From: attribution right at the top of the changelog. Please alter your scripts to include diffstat output after the ^--- Thanks. - 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
