From: Grant Grundler <grundler@parisc-linux.org>
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 22:49:42 -0700 [thread overview]
Message-ID: <20040222054942.GD30849@colo.lackof.org> (raw)
In-Reply-To: <20040220182140.GC11824@parcelfarce.linux.theplanet.co.uk>
On Fri, Feb 20, 2004 at 06:21:40PM +0000, Matthew Wilcox wrote:
> Unlikely. As I recall, the N4k diagram looks like this:
Beautiful diagram! (I'm saving that one)
And I confirmed it is correct in case anyone had doubts.
(I did)
> So the RAM is uniformly-accessible from all CPUs, but the IO is not.
I don't think there is much penalty for CPU's to access MMIO space
on "the other side". MMIO reads are so expensive anyway, I'd doubt
it would make that much difference.
> 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'm pretty sure it will look like this:
RAM Phys Address
0-2GB -> 0-2GB
-> 2-4GB I/O Space (mostly PCI MMIO)
2-4GB -> 4-6GB (courtesy of the memory controller)
The N-class was the first box which has an I/O hole from 2-4GB
physical address range. I hope Joel will be able to confirm this.
If not, I likely have documentation to confirm this.
grant
next prev parent reply other threads:[~2004-02-22 5:49 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
2004-02-22 5:49 ` Grant Grundler [this message]
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=20040222054942.GD30849@colo.lackof.org \
--to=grundler@parisc-linux.org \
--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