From: "Matthew Starzewski" <mstarzewski@xes-inc.com>
To: "Thomas Petazzoni" <thomas.petazzoni@enix.org>
Cc: <linux-mips@linux-mips.org>
Subject: Re: Using more than 256 MB of memory on SB1250 in 32-bit mode, revisited
Date: Fri, 10 Dec 2004 08:46:52 -0600 [thread overview]
Message-ID: <073a01c4dec7$184527a0$0d00340a@matts> (raw)
In-Reply-To: 41B96281.2050806@enix.org
> I'm really unsure of what I'll say, but I've seen people on this list
> talking about CONFIG_DISCONTIGMEM, an option for the kernel, which is :
>
> "Say Y to upport efficient handling of discontiguous physical memory,
> for architectures which are either NUMA (Non-Uniform Memory Access)
> or have huge holes in the physical address space for other reasons.
> See <file:Documentation/vm/numa> for more."
I've tried using DISCONTIGMEM on the MIPS32 build, but it yields the
following build error. Maybe someone familiar w/ the SGI IP27 (Origin 200
and
2000) code could tell us whether simply turning on DISCONTIGMEM is
a good idea.
include/linux/mmzone.h:364:2: #error NODES_SHIFT > MAX_NODES_SHIFT
Also, even if it compiled with DISCONTIGMEM, a look at
sgi-ip27/ip27-memory.c
shows no sign of HIGHMEM support, what I was depending on to use the upper
256MB of memory as per my original email. Now this may be OK; depending on
how
flexible the DISCONTIGMEM option is, perhaps I could map a wired TLB or
KSEG3
to the 2nd 256MB.
Thoughts?
Matt
----- Original Message -----
From: "Thomas Petazzoni" <thomas.petazzoni@enix.org>
To: "Matthew Starzewski" <mstarzewski@xes-inc.com>
Cc: <linux-mips@linux-mips.org>; <Steve.Finney@SpirentCom.COM>
Sent: Friday, December 10, 2004 2:46 AM
Subject: Re: Using more than 256 MB of memory on SB1250 in 32-bit mode,
revisited
WARNING: multiple messages have this Message-ID (diff)
From: "Matthew Starzewski" <mstarzewski@xes-inc.com>
To: Thomas Petazzoni <thomas.petazzoni@enix.org>
Cc: linux-mips@linux-mips.org
Subject: Re: Using more than 256 MB of memory on SB1250 in 32-bit mode, revisited
Date: Fri, 10 Dec 2004 08:46:52 -0600 [thread overview]
Message-ID: <073a01c4dec7$184527a0$0d00340a@matts> (raw)
Message-ID: <20041210144652.-UNEmozKXf8IfSADi3ZZ3-8iNM7505cD515YU6XxpbY@z> (raw)
In-Reply-To: 41B96281.2050806@enix.org
> I'm really unsure of what I'll say, but I've seen people on this list
> talking about CONFIG_DISCONTIGMEM, an option for the kernel, which is :
>
> "Say Y to upport efficient handling of discontiguous physical memory,
> for architectures which are either NUMA (Non-Uniform Memory Access)
> or have huge holes in the physical address space for other reasons.
> See <file:Documentation/vm/numa> for more."
I've tried using DISCONTIGMEM on the MIPS32 build, but it yields the
following build error. Maybe someone familiar w/ the SGI IP27 (Origin 200
and
2000) code could tell us whether simply turning on DISCONTIGMEM is
a good idea.
include/linux/mmzone.h:364:2: #error NODES_SHIFT > MAX_NODES_SHIFT
Also, even if it compiled with DISCONTIGMEM, a look at
sgi-ip27/ip27-memory.c
shows no sign of HIGHMEM support, what I was depending on to use the upper
256MB of memory as per my original email. Now this may be OK; depending on
how
flexible the DISCONTIGMEM option is, perhaps I could map a wired TLB or
KSEG3
to the 2nd 256MB.
Thoughts?
Matt
----- Original Message -----
From: "Thomas Petazzoni" <thomas.petazzoni@enix.org>
To: "Matthew Starzewski" <mstarzewski@xes-inc.com>
Cc: <linux-mips@linux-mips.org>; <Steve.Finney@SpirentCom.COM>
Sent: Friday, December 10, 2004 2:46 AM
Subject: Re: Using more than 256 MB of memory on SB1250 in 32-bit mode,
revisited
next prev parent reply other threads:[~2004-12-10 14:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 22:49 Using more than 256 MB of memory on SB1250 in 32-bit mode, revisited Matthew Starzewski
2004-12-09 22:49 ` Matthew Starzewski
2004-12-10 8:46 ` Thomas Petazzoni
2004-12-10 13:02 ` Maciej W. Rozycki
2004-12-10 14:46 ` Matthew Starzewski [this message]
2004-12-10 14:46 ` Matthew Starzewski
2004-12-10 16:10 ` Thomas Petazzoni
2004-12-15 15:02 ` Matthew Starzewski
2004-12-15 15:02 ` Matthew Starzewski
2004-12-15 14:56 ` Ralf Baechle
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='073a01c4dec7$184527a0$0d00340a@matts' \
--to=mstarzewski@xes-inc.com \
--cc=linux-mips@linux-mips.org \
--cc=thomas.petazzoni@enix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox