From: Christoph Lameter <cl@linux-foundation.org>
To: Dave Hansen <dave@linux.vnet.ibm.com>
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>
Subject: Re: sparsemem support for mips with highmem
Date: Mon, 18 Aug 2008 16:33:29 -0500 [thread overview]
Message-ID: <48A9EAA9.1080909@linux-foundation.org> (raw)
In-Reply-To: <1219094865.23641.118.camel@nimitz>
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).
--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-08-18 21:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 22:05 C Michael Sundius
2008-08-14 22:35 ` Dave Hansen
2008-08-14 23:16 ` C Michael Sundius
2008-08-14 23:52 ` C Michael Sundius
2008-08-15 0:02 ` Dave Hansen
2008-08-15 8:03 ` Thomas Bogendoerfer
2008-08-15 15:48 ` Dave Hansen
2008-08-15 16:12 ` C Michael Sundius
2008-08-15 16:20 ` Dave Hansen
2008-08-15 16:33 ` Thomas Bogendoerfer
2008-08-15 17:16 ` C Michael Sundius
2008-08-15 17:37 ` Dave Hansen
2008-08-15 18:17 ` C Michael Sundius
2008-08-15 18:23 ` Dave Hansen
2008-08-16 20:07 ` Thomas Bogendoerfer
2008-08-18 16:44 ` Randy Dunlap
2008-08-18 21:24 ` Christoph Lameter
2008-08-18 21:27 ` Dave Hansen
2008-08-18 21:33 ` Christoph Lameter [this message]
2009-01-16 21:46 ` Michael Sundius
2009-01-21 14:39 ` Christoph Lameter
2008-08-18 21:57 ` David VomLehn
2008-08-19 13:06 ` Christoph Lameter
2008-08-19 23:38 ` David VomLehn
2008-08-19 23:53 ` Jon Fraser
2008-08-20 13:58 ` Christoph Lameter
2008-08-20 19:28 ` David VomLehn
2008-08-20 20:51 ` Christoph Lameter
2008-08-15 16:30 ` Thomas Bogendoerfer
2008-08-26 9:09 ` Andy Whitcroft
2008-10-06 20:15 ` Have ever checked in your mips sparsemem code into mips-linux tree? C Michael Sundius
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48A9EAA9.1080909@linux-foundation.org \
--to=cl@linux-foundation.org \
--cc=Michael.sundius@sciatl.com \
--cc=apw@shadowen.org \
--cc=dave@linux.vnet.ibm.com \
--cc=jfraser@broadcom.com \
--cc=linux-mips@linux-mips.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@xenotime.net \
--cc=tsbogend@alpha.franken.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox