linux-mips
[Top] [All Lists]

RE: sparse or discontiguous memory on 32bit mips platform

To: <jfraser@broadcom.com>
Subject: RE: sparse or discontiguous memory on 32bit mips platform
From: "Sundius, Michael" <michael.sundius@sciatl.com>
Date: Mon, 14 Jul 2008 10:20:54 -0700
Authentication-results: sj-dkim-1; header.From=michael.sundius@sciatl.com; dkim=neutral
Cc: <linux-mips@linux-mips.org>, <msundius@sundius.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <D331130DD3DA194B96EF57DA3415F50A026331BB@SAUSCUPEXCH01.corp.sa.net> <1216054738.30304.45.camel@chaos.ne.broadcom.com>
Sender: linux-mips-bounce@linux-mips.org
Thread-index: Acjl0vODLU3QLKT5RlK8KXJW2TxnzAAAwV7r
Thread-topic: sparse or discontiguous memory on 32bit mips platform


| I have something similar.  Under 2.6.24, I have the following
| configured:
|
| CONFIG_HIGHMEM=y
| CONFIG_CPU_SUPPORTS_HIGHMEM=y
| CONFIG_SYS_SUPPORTS_HIGHMEM=y
| CONFIG_ARCH_FLATMEM_ENABLE=y
| CONFIG_ARCH_DISCONTIGMEM_ENABLE=y
| CONFIG_DISCONTIGMEM=y
| CONFIG_FLAT_NODE_MEM_MAP=y
| CONFIG_ARCH_POPULATES_NODE_MAP=y
| CONFIG_NODES_SHIFT=6
| CONFIG_FLAT_NODE_MEM_MAP=y
| CONFIG_NEED_MULTIPLE_NODES=y
|
|
| Each bank of memory is in a separate node. I did have to write
| some code in arch/mips/kernel/setup.c to setup the multiple memory
| regions.  I used some of the PPC NUMA code as an example, IIRC.
|
| Because my second bank of mem starts at 0x20000000,
| I use HIGHMEM to access it.  There been some HIGHMEM info
| posted to this list in the last 6 months.
|
| I didn't think my efforts were general enough to post, but maybe
| more people are doing these discontiguous memory platforms.

Oh, yes, that is very similar to what I want to do. we currently
use HIGHMEM to access our 2nd bank of memory, and so its the
setup of the additional node that we'd like to use. I'd be
interested in seeing that patch if possible.

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.
<Prev in Thread] Current Thread [Next in Thread>