From: C Michael Sundius <Michael.sundius@sciatl.com>
To: linux-mm@kvack.org, linux-mips@linux-mips.org,
jfraser@broadcom.com, Andy Whitcroft <apw@shadowen.org>,
Dave Hansen <dave@linux.vnet.ibm.com>
Subject: sparsemem support for mips with highmem
Date: Thu, 14 Aug 2008 15:05:45 -0700 [thread overview]
Message-ID: <48A4AC39.7020707@sciatl.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
Hi
I just got sparsemem working on our MIPS 32 platform. I'm not sure if
anyone
has done that before since there seems to be a couple of problems in the
arch specific code.
Well I realize that it is blazingly simple to turn on sparsemem, but for
the idiots (like myself)
out there I created a howto file to put in the Documentation directory
just because I thought
it would be a good idea to have some official info on it written down
somewhere.
it saved me a ton of space by the way. it seems to work great.
Mike
next reply other threads:[~2008-08-14 22:06 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 22:05 C Michael Sundius [this message]
2008-08-14 22:35 ` sparsemem support for mips with highmem Dave Hansen
2008-08-14 22:35 ` Dave Hansen
2008-08-14 23:16 ` C Michael Sundius
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 0:02 ` Dave Hansen
2008-08-15 8:03 ` Thomas Bogendoerfer
2008-08-15 8:03 ` Thomas Bogendoerfer
2008-08-15 15:48 ` Dave Hansen
2008-08-15 15:48 ` Dave Hansen
2008-08-15 16:12 ` C Michael Sundius
2008-08-15 16:12 ` C Michael Sundius
2008-08-15 16:20 ` Dave Hansen
2008-08-15 16:20 ` Dave Hansen
2008-08-15 16:33 ` Thomas Bogendoerfer
2008-08-15 16:33 ` Thomas Bogendoerfer
2008-08-15 17:16 ` C Michael Sundius
2008-08-15 17:16 ` C Michael Sundius
2008-08-15 17:37 ` Dave Hansen
2008-08-15 17:37 ` Dave Hansen
2008-08-15 18:17 ` C Michael Sundius
2008-08-15 18:17 ` C Michael Sundius
2008-08-15 18:23 ` Dave Hansen
2008-08-15 18:23 ` Dave Hansen
2008-08-16 20:07 ` Thomas Bogendoerfer
2008-08-16 20:07 ` Thomas Bogendoerfer
2008-08-18 16:44 ` Randy Dunlap
2008-08-18 16:44 ` Randy Dunlap
2008-08-18 21:24 ` Christoph Lameter
2008-08-18 21:24 ` Christoph Lameter
2008-08-18 21:27 ` Dave Hansen
2008-08-18 21:27 ` Dave Hansen
2008-08-18 21:33 ` Christoph Lameter
2008-08-18 21:33 ` Christoph Lameter
2009-01-16 21:46 ` Michael Sundius
2009-01-16 21:46 ` Michael Sundius
2009-01-21 14:39 ` Christoph Lameter
2009-01-21 14:39 ` Christoph Lameter
2008-08-18 21:57 ` David VomLehn
2008-08-18 21:57 ` David VomLehn
2008-08-19 13:06 ` Christoph Lameter
2008-08-19 13:06 ` Christoph Lameter
2008-08-19 23:38 ` David VomLehn
2008-08-19 23:38 ` David VomLehn
2008-08-19 23:53 ` Jon Fraser
2008-08-19 23:53 ` Jon Fraser
2008-08-20 13:58 ` Christoph Lameter
2008-08-20 13:58 ` Christoph Lameter
2008-08-20 19:28 ` David VomLehn
2008-08-20 19:28 ` David VomLehn
2008-08-20 20:51 ` Christoph Lameter
2008-08-20 20:51 ` Christoph Lameter
2008-08-15 16:30 ` Thomas Bogendoerfer
2008-08-15 16:30 ` Thomas Bogendoerfer
2008-08-26 9:09 ` Andy Whitcroft
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=48A4AC39.7020707@sciatl.com \
--to=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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.