Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Bradley D. LaRonde" <brad@ltc.com>
To: "Geert Uytterhoeven" <geert@linux-m68k.org>
Cc: <sjhill@cotw.com>, "linux-mips" <linux-mips@oss.sgi.com>
Subject: Re: What is the maximum physical RAM for a 32bit MIPS core?
Date: Wed, 6 Feb 2002 09:14:53 -0500	[thread overview]
Message-ID: <002f01c1af18$a8685410$5601010a@prefect> (raw)
In-Reply-To: Pine.GSO.4.21.0202060948190.20126-100000@vervain.sonytel.be

----- Original Message -----
From: "Geert Uytterhoeven" <geert@linux-m68k.org>
To: "Bradley D. LaRonde" <brad@ltc.com>
Cc: <sjhill@cotw.com>; "linux-mips" <linux-mips@oss.sgi.com>
Sent: Wednesday, February 06, 2002 3:49 AM
Subject: Re: What is the maximum physical RAM for a 32bit MIPS core?


> On Tue, 5 Feb 2002, Bradley D. LaRonde wrote:
> > As already mentioned, a MIPS TLB entry typically can point with 36 bits
> > (that's 67TB of address space?) at physical memory.  If you have more
than
>
> At bit less: 64 GiB or approx. 69 GB :-)

Oops, yeah.  67TB seemed a little high.  :-P

Regards,
Brad

WARNING: multiple messages have this Message-ID (diff)
From: "Bradley D. LaRonde" <brad@ltc.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: sjhill@cotw.com, linux-mips <linux-mips@oss.sgi.com>
Subject: Re: What is the maximum physical RAM for a 32bit MIPS core?
Date: Wed, 6 Feb 2002 09:14:53 -0500	[thread overview]
Message-ID: <002f01c1af18$a8685410$5601010a@prefect> (raw)
Message-ID: <20020206141453.lV6fuHyCjQ2oBn5a5CO5fVDoqGMhpZz4HIpuQZlmZbs@z> (raw)
In-Reply-To: Pine.GSO.4.21.0202060948190.20126-100000@vervain.sonytel.be

----- Original Message -----
From: "Geert Uytterhoeven" <geert@linux-m68k.org>
To: "Bradley D. LaRonde" <brad@ltc.com>
Cc: <sjhill@cotw.com>; "linux-mips" <linux-mips@oss.sgi.com>
Sent: Wednesday, February 06, 2002 3:49 AM
Subject: Re: What is the maximum physical RAM for a 32bit MIPS core?


> On Tue, 5 Feb 2002, Bradley D. LaRonde wrote:
> > As already mentioned, a MIPS TLB entry typically can point with 36 bits
> > (that's 67TB of address space?) at physical memory.  If you have more
than
>
> At bit less: 64 GiB or approx. 69 GB :-)

Oops, yeah.  67TB seemed a little high.  :-P

Regards,
Brad

  parent reply	other threads:[~2002-02-06 14:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-05 16:50 What is the maximum physical RAM for a 32bit MIPS core? Steven J. Hill
2002-02-05 17:47 ` 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 [this message]
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='002f01c1af18$a8685410$5601010a@prefect' \
    --to=brad@ltc.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-mips@oss.sgi.com \
    --cc=sjhill@cotw.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox