Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "William J. Earl" <wje@fir.engr.sgi.com>
To: "Greg Chesson" <greg@xtp.engr.sgi.com>
Cc: ralf@uni-koblenz.de, Alex deVries <adevries@engsoc.carleton.ca>,
	Igor Loncarevic <anubis@BanjaLuka.NET>,
	SGI Linux <linux@cthulhu.engr.sgi.com>
Subject: Re: What about...
Date: Fri, 17 Jul 1998 11:19:54 -0700	[thread overview]
Message-ID: <199807171819.LAA12327@fir.engr.sgi.com> (raw)
In-Reply-To: <9807171101.ZM18755@xtp.engr.sgi.com>

Greg Chesson writes:
...
 > Linux has proven to be worthwhile as a node controller in an MPP architecture -
 > that's what a Beowolf is.  But that does not make it ready for SMP nodes
 > that scale to large numbers.  It seems wasteful to program a large scale
 > ccNUMA machine the same way as a Beowolf cluster: you'd be throwing away
 > most of the capabilities of the hardware.  That's why I don't
 > think it is interesting or particularly useful... unless a massive amount
 > of work went into rewriting the io and memory management subsystems,
 > not to mention scheduling, administration, etc.
...

     I expect that much of the work will gradually happen in linux, once
the remaining small-CPU-count issues are resolved.  Right now, there
is no shortage of interesting problems to attack.  :-)

     One possible way to approach the large-CPU-count space with linux
is to indeed run multiple linux kernels, one per node in a ccNUMA
machine, and add a distributed OS layer at a fairly high level.  If it
is not underway already somewhere, I would expect someone to take up
the project as a graduate school project.  Some systems of this sort
have been built or attempted, with varying degrees of success.  Given
the linux bias toward small and simple, a linux-based distributed OS
might actually work.

     One important ingredient in such a system, which would be
valuable immediately for clusters, would be a efficient distributed
volume manager and file system.  

     In any case, trying to port linux straight to a large ccNUMA 
(or even a large SMP) system would be a lot of effort for limited
return at present.

  reply	other threads:[~1998-07-17 18:21 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 [this message]
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

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=199807171819.LAA12327@fir.engr.sgi.com \
    --to=wje@fir.engr.sgi.com \
    --cc=adevries@engsoc.carleton.ca \
    --cc=anubis@BanjaLuka.NET \
    --cc=greg@xtp.engr.sgi.com \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=ralf@uni-koblenz.de \
    /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