From: Christoph Lameter <cl@linux-foundation.org>
To: Michael Sundius <msundius@cisco.com>
Cc: Dave Hansen <dave@linux.vnet.ibm.com>,
Randy Dunlap <rdunlap@xenotime.net>,
"Sundius, Michael" <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>,
msundius@sundius.com
Subject: Re: sparsemem support for mips with highmem
Date: Wed, 21 Jan 2009 09:39:50 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.1.10.0901210938120.7424@qirst.com> (raw)
In-Reply-To: <4971002D.2090907@cisco.com>
On Fri, 16 Jan 2009, Michael Sundius wrote:
> you said that the simplest configuration is to use vmalloc for the populate
> function.
> could you expand on that? (i didn't see that the populate function used
> vmalloc or maybe
> we are talking about a different populate function).
If you place the vmemmap in the vmalloc area then its easy to reserve
virtual space for the vmemmap. You can use the vmalloc populate functions
to populate the vmemmap.
> this work w/ mips which i understand uses only 2 levels can I just take out
> the part of
> the function that sets up the middle level table?
Sure. Hoever, the vmemmap populate stuff will do that automagically for
you.
--
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:[~2009-01-21 14:43 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
2009-01-16 21:46 ` Michael Sundius
2009-01-21 14:39 ` Christoph Lameter [this message]
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=alpine.DEB.1.10.0901210938120.7424@qirst.com \
--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=msundius@cisco.com \
--cc=msundius@sundius.com \
--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