From: "William J. Earl" <wje@fir.engr.sgi.com>
To: Christian Reisch <creisch@cthulhu.engr.sgi.com>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Linux on the O2
Date: Tue, 2 Dec 1997 15:45:27 -0800 [thread overview]
Message-ID: <199712022345.PAA05569@fir.engr.sgi.com> (raw)
In-Reply-To: <34849AA8.F21FFE4E@engr.sgi.com>
Christian Reisch writes:
> William J. Earl wrote:
> O2 is also a bigger technical problem, even with specifications in
> hand.
> > The drivers are actually easier than for Indy, but really exploiting the
> > O2 capabilities in graphics and digital media required a lot of enhancements
> > to the memory management, since O2 is a UMA system. You could do a dumb
> > port, with a fixed frame buffer size, but then most of the O2 is wasted.
>
> Actually I suspect the exact opposite would happen and hence
> management's fear. There are ALOT more people in the linux community
> than we have working at SGI. It is very concievable that if the specs
> were
> available linux on O2 would massively out perform irix on the O2. This
> would
> be a major embarrassment to the company. Compare and contrast as Unixes
> Solaris X86 and Linux on a given x86 box or Digital Unix and linux on an
> alpha.
Many of us who want to see Linux on SGI systems expect that Linux
will be substantially faster on a number of primitive functions, especially
on uniprocessor systems. We think of this as a nice club to persuade people
that low-level performance (a cache miss here and 100 instructions there)
really matters.
What I was talking about in regard to O2 was exploiting the
hardware functionality, such as the ability to use 100 MB of memory
for Photoshop, and then switch in seconds to using 100 MB of memory
for texture mapping, including real-time texture mapping of live
video. Some of this is fairly generic library work, but some of it
requires fundamental changes to the operating system memory management
(assuming you do not impose a fixed partitioning of memory).
> Quality wise free software always beats proprietary software (if for
> no other reason than it has to make fewer concesions to release
> schedules
> and politics) often embarassingly so.
That is not always the case. It is the case for GNU and Linux
software, due to the constraints imposed on the development and release
process, which tend to keep untested changes out of the main tree.
next prev parent reply other threads:[~1997-12-02 23:49 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-02 21:50 Linux on the O2 cypher
1997-12-02 22:10 ` Ralf Baechle
1997-12-02 22:31 ` Ariel Faigon
1997-12-02 22:31 ` Ariel Faigon
1997-12-03 0:04 ` Alan Cox
1997-12-03 0:46 ` John Wiederhirn
1997-12-03 3:06 ` William J. Earl
1997-12-03 3:06 ` William J. Earl
1997-12-03 18:28 ` cypher
1997-12-03 1:51 ` Douglas F. Elznic
1997-12-03 1:51 ` Douglas F. Elznic
1997-12-03 7:01 ` ralf
[not found] ` <Pine.LNX.3.95.971203132942.15095B-100000@vertigo.cs.indian a.edu>
1997-12-03 18:04 ` Douglas F. Elznic
1997-12-03 18:39 ` Alan Cox
1997-12-03 18:39 ` Alan Cox
1997-12-03 18:42 ` cypher
1997-12-03 18:49 ` cypher
1997-12-03 18:05 ` David Chatterton
1997-12-03 2:34 ` Brendan Black
1997-12-03 2:58 ` Richard Offer
1997-12-03 3:19 ` Douglas F. Elznic
1997-12-03 8:21 ` Oliver Frommel
1997-12-03 10:51 ` Alan Cox
1997-12-03 10:51 ` Alan Cox
1997-12-03 18:32 ` cypher
1997-12-03 18:31 ` cypher
1997-12-03 21:19 ` Warner Losh
1997-12-03 22:16 ` Chad Campbell
1997-12-03 22:31 ` William J. Earl
1997-12-03 22:48 ` Alan Cox
1997-12-03 22:48 ` Alan Cox
[not found] ` <Pine.LNX.3.95.971203161250.15277A-100000@dv123s34.lawrence .ks.us>
1997-12-03 22:38 ` Douglas F. Elznic
1997-12-02 22:33 ` William J. Earl
1997-12-02 23:32 ` Christian Reisch
1997-12-02 23:45 ` William J. Earl [this message]
1997-12-03 0:09 ` Alan Cox
1997-12-03 0:09 ` Alan Cox
1997-12-03 7:46 ` Chris Carlson
1997-12-04 5:39 ` Lige Hensley
1997-12-04 5:39 ` Lige Hensley
1997-12-04 5:48 ` David S. Miller
1997-12-04 16:55 ` Greg Chesson
1997-12-04 16:51 ` Greg Chesson
1997-12-04 22:08 ` David Chatterton
1997-12-04 14:06 ` Lige Hensley
1997-12-04 17:03 ` Greg Chesson
1997-12-04 17:22 ` William J. Earl
1997-12-04 18:59 ` Alan Cox
1997-12-04 18:59 ` Alan Cox
1997-12-04 22:01 ` ralf
1997-12-04 23:33 ` William J. Earl
1997-12-05 1:33 ` ralf
1997-12-05 3:25 ` Chad Campbell
1997-12-04 18:54 ` Alan Cox
1997-12-04 18:54 ` Alan Cox
1997-12-04 19:41 ` Alex deVries
1997-12-04 22:28 ` Eric Kimminau
1997-12-04 22:44 ` Alan Cox
1997-12-05 0:17 ` ralf
1997-12-05 9:06 ` Alan Cox
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=199712022345.PAA05569@fir.engr.sgi.com \
--to=wje@fir.engr.sgi.com \
--cc=creisch@cthulhu.engr.sgi.com \
--cc=linux@cthulhu.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