Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Greg Chesson" <greg@xtp.engr.sgi.com>
To: ralf@uni-koblenz.de, 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: Fri, 17 Jul 1998 18:58:07 -0700	[thread overview]
Message-ID: <9807171858.ZM19563@xtp.engr.sgi.com> (raw)
In-Reply-To: ralf@uni-koblenz.de "Re: What about..." (Jul 18,  3:37am)

I think everyone is suggesting the same general path, and I'm gratified
to know that the buddy system code anticipates non-contiguous physical
memory.

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.

g

-- 
Greg Chesson

  reply	other threads:[~1998-07-18  1:58 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 [this message]
1998-07-18  2:44                 ` ralf
1998-07-18 10:47                   ` ralf

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=9807171858.ZM19563@xtp.engr.sgi.com \
    --to=greg@xtp.engr.sgi.com \
    --cc=adevries@engsoc.carleton.ca \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=anubis@BanjaLuka.NET \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=ralf@uni-koblenz.de \
    --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