linux-mips
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: sparsemem support for mips with highmem

from [Dave Hansen] [Permanent Link][Original]
To: Christoph Lameter <cl@linux-foundation.org>
Subject: Re: sparsemem support for mips with highmem
From: Dave Hansen <dave@linux.vnet.ibm.com>
Date: Mon, 18 Aug 2008 14:27:45 -0700
Cc: Randy Dunlap <rdunlap@xenotime.net>, C Michael Sundius <Michael.sundius@sciatl.com>, Thomas Bogendoerfer <tsbogend@alpha.franken.de>, linux-mm@kvack.org, linux-mips@linux-mips.org, jfraser@broadcom.com, Andy Whitcroft <apw@shadowen.org>
In-reply-to: <48A9E89C.4020408@linux-foundation.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <48A4AC39.7020707@sciatl.com> <1218753308.23641.56.camel@nimitz> <48A4C542.5000308@sciatl.com> <20080815080331.GA6689@alpha.franken.de> <1218815299.23641.80.camel@nimitz> <48A5AADE.1050808@sciatl.com> <20080815163302.GA9846@alpha.franken.de> <48A5B9F1.3080201@sciatl.com> <1218821875.23641.103.camel@nimitz> <48A5C831.3070002@sciatl.com> <20080818094412.09086445.rdunlap@xenotime.net> <48A9E89C.4020408@linux-foundation.org>
Sender: linux-mips-bounce@linux-mips.org 
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?

-- Dave
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: sparsemem support for mips with highmem, Christoph Lameter
Next by Date:  Re: [MIPS] msp71xx: resolve compilation problem in msp_setup.c, Ralf Baechle
Previous by Thread:  Re: sparsemem support for mips with highmem, Christoph Lameter
Next by Thread:  Re: sparsemem support for mips with highmem, Christoph Lameter
Indexes:  [Date] [Thread] [Top] [All Lists]