linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: C Michael Sundius <Michael.sundius@sciatl.com>
To: linux-mm@kvack.org
Cc: msundius@sundius.com
Subject: sparcemem or discontig?
Date: Tue, 29 Jul 2008 11:11:43 -0700	[thread overview]
Message-ID: <488F5D5F.9010006@sciatl.com> (raw)

Hi,

I'm working on a 32bit mips 1 cpu platform that has 2 large banks of
memory that are discontiguous in the physical address space. That is to
say there is a large hole in between them. We are using the 2.6.24
kernel. In order to save memory on page tables, we'd like to employ the
use of either the CONFIG_SPARCEMEM, or CONFIG_DISCONTIG configuration
options, but I'm a bit unsure which I should use.

My understanding is that SPARCEMEM is the way of the future, and since
I don't really have a NUMA machine, maybe sparcemem is more appropriate,
yes? On the other hand I can't find much info about how it works or how
to add support for it on an architecture that has here-to-fore not
supported that option.

Is there anywhere that there is a paper or rfp that describes how the
spacemem (or discontig) features work (and/or the differences between
then)? Has anyone out there done this for MIPS32? has anyone had
experience with adding support for either sparcemem or discontig on an
arch before , that could give me a their thoughts the process or "gotchas"?

thanks
Mike



     - - - - -                              Cisco                            - - - - -         
This e-mail and any attachments may contain information which is confidential, 
proprietary, privileged or otherwise protected by law. The information is solely 
intended for the named addressee (or a person responsible for delivering it to 
the addressee). If you are not the intended recipient of this message, you are 
not authorized to read, print, retain, copy or disseminate this message or any 
part of it. If you have received this e-mail in error, please notify the sender 
immediately by return e-mail and delete it from your computer.

--
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>

             reply	other threads:[~2008-07-29 18:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29 18:11 C Michael Sundius [this message]
2008-07-29 21:51 ` Dave Hansen
2008-07-30  9:35   ` Andy Whitcroft
2008-07-30 16:23     ` C Michael Sundius
2008-07-30 16:29       ` Dave Hansen
2008-08-05 21:39       ` Turning on Sparsemem C Michael Sundius
2008-08-05 21:56         ` Dave Hansen
2008-08-05 22:04           ` C Michael Sundius
2008-08-05 22:19             ` Dave Hansen

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=488F5D5F.9010006@sciatl.com \
    --to=michael.sundius@sciatl.com \
    --cc=linux-mm@kvack.org \
    --cc=msundius@sundius.com \
    /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