From: ralf@uni-koblenz.de
To: "William J. Earl" <wje@fir.engr.sgi.com>
Cc: 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 19:29:54 +0200 [thread overview]
Message-ID: <19980717192954.16464@uni-koblenz.de> (raw)
In-Reply-To: <199807171411.HAA11412@fir.engr.sgi.com>; from William J. Earl on Fri, Jul 17, 1998 at 07:11:42AM -0700
On Fri, Jul 17, 1998 at 07:11:42AM -0700, William J. Earl wrote:
> Greg Chesson writes:
> > Alex is right.
> > Linux on Origin 2000 would be a huge project - not just a port.
> ...
>
> Note that the reason it would be a big project is not so much the
> hardware itself, but rather the scale of the system. IRIX needed a lot
> of infrastructure work to be useful on very large system with a very large
> number of I/O buses and devices. That is, a toy port would not be all
> that giant a project, but it would not be particularly useful. If there
> were a good linux on some other very large ccNUMA machine, then an Origin
> port would be much simpler. By "good", I mean a linux which scale well
> for large (greater than 32) processor and I/O count (many I/O buses
> and thousands of disk). It expect such a linux will happen eventually,
> but not yet.
Actually some people begin to be interested in Linux for huge installations.
For example a bank recently offer us some machine time on a maximum
configuration (64 CPU, 64GB RAM) E10000 for porting Linux. This didn't
happen (yet?) for other reasons, but it shows that there is interest.
For the time being most large Linux installations are based on the Beowulf
clustering software - and I think place 318 on the list on the top 500 list
of supercomputer installations is quite remarkable for something which's
OS software is being shipped for USD 29.95 by RedHat.
Anyway, as far as our MIPS port goes we first need to implement SMP at
all before we should think about scaling. More about Linux in general -
most people are currentl using Linux/SMP on dual processors, few on
quad CPU systems and even fewer on larger systems. This is about where
the market of Linux and it's limits are. But the tradition of Linux
shows that technology for which a demand exists will be developed sooner
or later. Where Linux technology exists, usually a market will develop.
So far I see a demand for older SGI SMP systems, Origin 200 systems (quite
some inquiries) but not yet for Origin 2000 systems.
Ralf
next prev parent reply other threads:[~1998-07-17 17:33 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 [this message]
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
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=19980717192954.16464@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=adevries@engsoc.carleton.ca \
--cc=anubis@BanjaLuka.NET \
--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