Mike, I'll run some diffs and post them. It'll take a little bit for me to sort out the changes. I don't have a 'use second bank of memory' patch per se. You'll definitely want to pick up the HIGHMEM changes that were posted. If you have 4K pages and more than 16K of cache (assuming 4 cache ways), you need the patches to deal with cache aliases. Jon On Mon, 2008-07-14 at 10:20 -0700, Sundius, Michael wrote: > > | 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.
