[Top] [All Lists]

Re: sparsemem support for mips with highmem

To: Dave Hansen <>
Subject: Re: sparsemem support for mips with highmem
From: Christoph Lameter <>
Date: Mon, 18 Aug 2008 16:33:29 -0500
Cc: Randy Dunlap <>, C Michael Sundius <>, Thomas Bogendoerfer <>,,,, Andy Whitcroft <>
In-reply-to: <1219094865.23641.118.camel@nimitz>
Original-recipient: rfc822;
References: <> <1218753308.23641.56.camel@nimitz> <> <> <1218815299.23641.80.camel@nimitz> <> <> <> <1218821875.23641.103.camel@nimitz> <> <> <> <1219094865.23641.118.camel@nimitz>
User-agent: Thunderbird (Windows/20080708)
Dave Hansen wrote:
> On Mon, 2008-08-18 at 16:24 -0500, Christoph Lameter wrote:
>> This overhead can be avoided by configuring sparsemem to use a virtual 
>> vmemmap
>> (CONFIG_SPARSEMEM_VMEMMAP). In that case it can be used for non NUMA since 
>> the
>> overhead is less than even FLATMEM.
> Is that all it takes these days, or do you need some other arch-specific
> code to help out?

Some information is in mm/sparse-vmemmap.c. Simplest configuration is to use
vmalloc for the populate function. Otherwise the arch can do what it wants to
reduce the overhead of virtual mappings (in the x86 case we use a 2M TLB
entry, and since 2M TLBs are also used for the 1-1 physical mapping the
overhead is the same as for 1-1 mappings).

<Prev in Thread] Current Thread [Next in Thread>