Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Nigel Gamble <nigel@cthulhu.engr.sgi.com>
To: Alistair Lambie <alambie@wellington.sgi.com>
Cc: ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com
Subject: Re: Linux: the next step
Date: Fri, 02 Aug 1996 16:07:40 -0700	[thread overview]
Message-ID: <32028A3C.2781@engr.sgi.com> (raw)
In-Reply-To: 9608021537.ZM16832@windy.wellington.sgi.com

Alistair Lambie wrote:
>    To
>    emphasis this point I feel we need to have it run on any new platforms
>    at first shipment, and support the neat features.

Dream on!  Here in ISD (Indigo2 land), we're working flat out just to
get IRIX to run on any new platforms at first shipment, with all
the neat features supported.  I think you'll find the same
is true of all the other product divisions.

> One comment I would make here is that people really need to work out whether
> we are a hardware or software company.  I realise that this is probably
> contentious (sp?), but my feeling is that we are a company who make hardware,
> and the software is really a means to an end...selling more hardware.  If this
> is true, then people need to look at where we are going to get the greatest
> number of hardware sales from....Irix or Linux.  We need both I think to hit
> different markets, and maybe we even need NT (don't want to get into that
> argument!).  Maybe we should be getting agreement from management for funding
> based on sales, and I'll bet we can get a lot more mileage from the funding
> than Irix will :-)

We are neither a hardware company nor a software company.
We are a *systems* company.  We build the best computer systems
on the planet through a combination of hardware and software
working together.  If we replaced IRIX with NT, we would have
to cancel most of our high performance hardware projects, because
NT will not support the new systems.  As for Linux,
when will it support true symmetric multiprocessing with fine-grained
semaphore and mutex locking, and a fully preemptible kernel?
At the San Diego Usenix earlier this year, Linus Torvalds
thought that the probable answer was "not anytime soon".
(By the way, in order to do this correctly, every device driver would
have to be rewritten.)  Linux would need this *at a minimum* before
there is any hope that it would supplant IRIX on the current
generation of hardware, let alone any future new platforms.

-- 
Nigel Gamble       "Are we going to push the edge of the envelope,
Brain?"
Silicon Graphics   "No, Pinky, but we may get to the sticky part."
nigel@sgi.com
(415) 933-3109

  reply	other threads:[~1996-08-02 23:09 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-07-31  0:48 Linux: the next step Ariel Faigon
1996-08-02 15:37 ` Alistair Lambie
1996-08-02 23:07   ` Nigel Gamble [this message]
1996-08-02 23:54     ` David S. Miller
1996-08-03  0:12     ` Alistair Lambie
1996-08-03  0:12       ` Alistair Lambie
  -- strict thread matches above, loose matches on Subject: below --
1996-08-03  1:11 Larry McVoy
1996-08-12 20:32 Steve Alexander
1996-08-12 20:32 ` Steve Alexander
1996-08-12 20:52 ` Bob English
1996-08-12 20:52   ` Bob English
1996-08-12 21:09 Larry McVoy
1996-08-12 21:18 Steve Alexander
1996-08-12 21:18 ` Steve Alexander
1996-08-12 21:24 ` Bob English
1996-08-12 21:24   ` Bob English
1996-08-12 21:20 Steve Alexander
1996-08-12 21:20 ` Steve Alexander
     [not found] ` <sca@refugee.engr.sgi.com>
1996-08-12 21:35   ` Sandeep Cariapa
1996-08-12 21:39 ` John E. Schimmel
1996-08-12 21:39   ` John E. Schimmel
1996-08-12 21:49 Larry McVoy
1996-08-12 21:49 ` Larry McVoy
1996-08-12 22:59 ` Nigel Gamble
1996-08-12 22:59   ` Nigel Gamble
1996-08-12 23:31   ` Bob English
1996-08-12 23:31     ` Bob English
1996-08-13 11:45   ` David S. Miller
1996-08-13 11:45     ` David S. Miller
1996-08-13 15:36     ` Nigel Gamble
1996-08-13 16:45       ` Greg Chesson
1996-08-13 16:45         ` Greg Chesson

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=32028A3C.2781@engr.sgi.com \
    --to=nigel@cthulhu.engr.sgi.com \
    --cc=alambie@wellington.sgi.com \
    --cc=ariel@cthulhu.engr.sgi.com \
    --cc=linux@yon.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