All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steven J. Hill" <sjhill@cotw.com>
To: linux-mips@oss.sgi.com
Subject: What is the maximum physical RAM for a 32bit MIPS core?
Date: Tue, 05 Feb 2002 10:50:20 -0600	[thread overview]
Message-ID: <3C600D4C.43CBA784@cotw.com> (raw)

I am just trying to fill in some more MIPS knowledge here. With a 32-bit
MIPS processor, we are forever limited to a userspace of 2GB in size thanks
to the kuser region. kseg0/1 map the same 512MB of physical memory. kseg2
is 1GB in size and hence it could address another 1GB of RAM. So, is the
maximum amount of RAM for a 32bit MIPS core:

   1) 1.5GB = 0.5GB kseg0/1 + 1.0GB kseg2

   2) 4.0GB = largest 32-bit address

   3) Something larger than 4.0GB by adding fancy external HW logic

Also, for choice #3, while it would be a hit in performance, could you use
the fp registers for 64-bit pointers to address larger than 4.0GB?

Thanks in advance.

-Steve
      
-- 
 Steven J. Hill - Embedded SW Engineer

             reply	other threads:[~2002-02-05 16:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-05 16:50 Steven J. Hill [this message]
2002-02-05 17:47 ` What is the maximum physical RAM for a 32bit MIPS core? Hartvig Ekner
2002-02-05 20:46   ` Steven J. Hill
2002-02-05 20:53     ` Hartvig Ekner
2002-02-05 20:53       ` Hartvig Ekner
2002-02-05 21:15     ` Pete Popov
2002-02-05 21:24       ` Steven J. Hill
2002-02-05 21:44         ` Pete Popov
2002-02-05 21:58         ` Bradley D. LaRonde
2002-02-05 21:58           ` Bradley D. LaRonde
2002-02-06  8:49           ` Geert Uytterhoeven
2002-02-06 11:16             ` nick
2002-02-06 12:07               ` Geert Uytterhoeven
2002-02-06 14:14             ` Bradley D. LaRonde
2002-02-06 14:14               ` Bradley D. LaRonde
2002-02-06  5:29     ` Ralf Baechle
2002-02-06  2:33 ` Ralf Baechle
2002-02-06 13:17   ` William Lee Irwin III

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=3C600D4C.43CBA784@cotw.com \
    --to=sjhill@cotw.com \
    --cc=linux-mips@oss.sgi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.