Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: ralf@uni-koblenz.de
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Greg Chesson <greg@xtp.engr.sgi.com>
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 03:37:59 +0200	[thread overview]
Message-ID: <19980718033759.C378@uni-koblenz.de> (raw)
In-Reply-To: <m0yxF1A-000aOoC@the-village.bc.nu>; from Alan Cox on Fri, Jul 17, 1998 at 07:14:04PM +0100

On Fri, Jul 17, 1998 at 07:14:04PM +0100, Alan Cox wrote:

> > many "holes"...  The idea of a simple buddy-system allocator as is
> > ingrained in the Linux kernel falls apart completely in the face of
> > this kind of architecture.   I suppose you could run a copy of Linux
> > on every node, but I consider that an excuse rather than a solution.
> 
> Actually the Linux buddy stuff is quite happy with holes. Its still
> completely inappropriate. From the above I deduce we'd have to do
> mips64 before we even considerd it anyway

At least in Vger CVS we alredy have code to efficiently deal with
non-dense memory architectures with buddy.

I think the memory allocator design as presented by Rik van Riel looks as
if it is a good base to deal much more efficiently with such an
memory architecture.  And then there is Sct with his big iron experience
working on something better than the buddy system.

I completly agree that we first have to go to MIPS64 before we really
can attack big iron problems.  The current Linux/MIPS kernel design limits
the memory to the size of KSEG0 which is 512mb.  Putting Linux into a
64bit universe we'd extend that design limit to the size of XKSEG0, or
1TB for current silicon.

  Ralf

  parent reply	other threads:[~1998-07-18  1:39 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 [this message]
1998-07-18  1:58               ` Greg Chesson
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=19980718033759.C378@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