From: ralf@uni-koblenz.de
To: Greg Chesson <greg@xtp.engr.sgi.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: wje@fir.engr.sgi.com, adevries@engsoc.carleton.ca,
anubis@BanjaLuka.NET, linux@cthulhu.engr.sgi.com
Subject: Re: What about...
Date: Sat, 18 Jul 1998 12:47:54 +0200 [thread overview]
Message-ID: <19980718124754.C2575@uni-koblenz.de> (raw)
In-Reply-To: <19980718044403.F378@uni-koblenz.de>; from ralf@uni-koblenz.de on Sat, Jul 18, 1998 at 04:44:03AM +0200
On Sat, Jul 18, 1998 at 04:44:03AM +0200, ralf@uni-koblenz.de wrote:
> On Fri, Jul 17, 1998 at 06:58:07PM -0700, Greg Chesson wrote:
> > I think you'd want to extend the design limit (XKSEG0) beyond 1 TB
> > to handle the next rev of silicon. I'd suggest 64 TB (48 bits) as
> > the appropriate goal.
>
> As far as the maximum amount of RAM goes, no problem. The only assumption
> which I make is that the entire available memory is visible in XKSEG0,
> whatever it's size is. That means the actual design limit is the maximum
> possible size of XKSEG0 for the MIPS 64bit architecture which is 2^62 bytes.
Ooops, the real limit is of course how much memory can be presented in XKPHYS
which is a bit less, just 2^58 bytes or 4 exabytes. XKSEG or XKSSEG would
be used for kernel virtual memory which usually isn't used very much under
Linux - it's virtual, but not swappable.
Ralf
prev parent reply other threads:[~1998-07-18 10:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <35ADF6D0.46FCB21E@BanjaLuka.NET>
1998-07-17 5:24 ` What about Alex deVries
1998-07-17 5:30 ` Greg Chesson
1998-07-17 14:11 ` William J. Earl
1998-07-17 15:07 ` Alan Cox
1998-07-17 15:07 ` Alan Cox
1998-07-17 17:43 ` ralf
1998-07-17 17:53 ` Alan Cox
1998-07-17 22:15 ` Jeffrey Watts
1998-07-17 17:29 ` ralf
1998-07-17 18:01 ` Greg Chesson
1998-07-17 18:19 ` William J. Earl
1998-07-18 1:57 ` ralf
1998-07-18 2:00 ` Greg Chesson
[not found] ` <wje@fir>
1998-07-17 17:47 ` Greg Chesson
1998-07-17 18:14 ` Alan Cox
1998-07-17 18:14 ` Alan Cox
1998-07-17 18:21 ` William J. Earl
1998-07-17 18:21 ` William J. Earl
1998-07-18 1:37 ` ralf
1998-07-18 1:58 ` Greg Chesson
1998-07-18 2:44 ` ralf
1998-07-18 10:47 ` ralf [this message]
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=19980718124754.C2575@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=adevries@engsoc.carleton.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=anubis@BanjaLuka.NET \
--cc=greg@xtp.engr.sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=wje@fir.engr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox