Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Joel Soete <soete.joel@tiscali.be>
To: Matthew Wilcox <willy@debian.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Linux only see 2Gb of ram of N4k
Date: Sat, 21 Feb 2004 18:19:31 +0000	[thread overview]
Message-ID: <4037A133.5020906@tiscali.be> (raw)
In-Reply-To: <20040220182140.GC11824@parcelfarce.linux.theplanet.co.uk>



Matthew Wilcox wrote:
> On Fri, Feb 20, 2004 at 07:04:26PM +0100, Joel Soete wrote:
> 
>>Hi all,
>>
>>My collegue make me notice that the N4k on which I can test Linux was supplied
>>with 4Gb of ram (which if confirm at boot prompt) but Linux only see 2Gb.
>>
>>It is a dual cpu machine, is that 1/2 ram dedicated to 1 cpu and the other
>>1/2 to the 2d cpu?
> 
> 
> Unlikely.  As I recall, the N4k diagram looks like this:
> 
> <-PCI-> Elroy <-Ropes\      PA <-+-> PA        PA <-+-> PA       /Ropes-> Elroy
> <-PCI-> Elroy <-Ropes-\         DEW       RAM      DEW          /-Ropes-> Elroy
> <-PCI-> Elroy <-Ropes--> IKE <-Merced-> Stretch <-Merced-> IKE <--Ropes-> Elroy
> <-PCI-> Elroy <-Ropes-/         DEW       RAM      DEW          \-Ropes-> Elroy
> <-PCI-> Elroy <-Ropes/      PA <-+-> PA        PA <-+-> PA       \Ropes-> Elroy
> 
> So the RAM is uniformly-accessible from all CPUs, but the IO is not.

That is also what I believe to have understood from our previous talk about N Stretch mmu
(but I am never sure to well undertand, thanks to confirm)

> 
> If you look at pat_memconfig() in arch/parisc/kernel/inventory.c, you'll
> see how we try to figure out what memory ranges are in the machine.
> Want to try debugging that, see what's being reported by firmware?
> 
I will try.

Many thanks,
	Joel

  reply	other threads:[~2004-02-21 18:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-20 18:04 [parisc-linux] Linux only see 2Gb of ram of N4k Joel Soete
2004-02-20 18:21 ` Matthew Wilcox
2004-02-21 18:19   ` Joel Soete [this message]
2004-02-22  5:49   ` Grant Grundler
2004-02-23  8:30     ` Joel Soete
2004-03-23 15:07       ` Joel Soete
2004-03-24 16:42         ` Joel Soete
2004-03-24 17:39           ` Grant Grundler
2004-03-24 18:23             ` Joel Soete

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=4037A133.5020906@tiscali.be \
    --to=soete.joel@tiscali.be \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=willy@debian.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