> 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@xxxxxxxx> To: "Matthew Starzewski" <mstarzewski@xxxxxxxxxxx> Cc: <linux-mips@xxxxxxxxxxxxxx>; <Steve.Finney@xxxxxxxxxxxxxx> Sent: Friday, December 10, 2004 2:46 AM Subject: Re: Using more than 256 MB of memory on SB1250 in 32-bit mode, revisited
