Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: offer@morgaine.engr.sgi.com (Richard Offer)
To: linux@cthulhu.engr.sgi.com
Subject: Re: [Fwd: linus.linux.sgi.com]
Date: Tue, 19 Jan 1999 18:28:50 -0800 (PST)	[thread overview]
Message-ID: <9901191828.ZM20761@morgaine.engr.sgi.com> (raw)
In-Reply-To: job bogan <job@piquin.uchicago.edu> "Re: [Fwd: linus.linux.sgi.com]" (Jan 19,  8:04pm)


* $ from job@piquin.uchicago.edu at "19-Jan: 8:04pm" | sed "1,$s/^/* /"
*
*
* Your message dated: Tue, 19 Jan 1999 19:29:16 CST
*
* >The current mainstream memory offering is 70n/s and we are at 50n/s.  The
memo
* >ry is not proprietary - any manufacturer could buy it if their system could
dr
* >ive it fast enough!
*
* pardon me but...
* Cut the SGI - "We Are Better Than God, Bow Before Our I/O" crap.
*
* Lots of PCs use 10ns SDRAM and 6ns SDRAM all of the time.

Well, I couldn't see anything faster than 60ns on Kingstons store.
http://www.ec.kingston.com/ecom/kepler/specs.asp

*
* Humm, a look at the glossies for the 320 and 540 make it look like all
* of SGI is working off a typo.  It lists:
*    * 100 MHz (50 ns) ECC synchronous dynamic RAM (SDRAM)
* that should read 5ns.  and beyond that, lots of people sell 100Mhz
* capable SDRAM.  (eg http://www.memoryx.com/generic.htm)

I'd guess that their 10ns is a misprint as its cheap and listed in the PC-66
section.


Isn't 100Mhz and 50ns a measure of two different things ? This is meant as a
serious question, as I don't know.  But, I'd guess that one is the refresh and
one the time to access ?

*
* I might buy some if they are competitive w/ plain old white Linux boxes.

How do you measure 'competitive' ? For me, they aren't; for my next-cubicle
neighbour they would be. Luckily we don't live in a one size
(hardware/software) fits all world.

* job
*

richard.

_______________________________________________________________________

A guest signature by Dan Boyd (boyd at cs.buffalo.edu)

  A competent sysadmin can turn any task into one resembling system
  administration and requiring a Makefile.

  parent reply	other threads:[~1999-01-20  2:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-19 23:28 [Fwd: linus.linux.sgi.com] dmanddmer
1999-01-19 23:28 ` dmanddmer
1999-01-20  1:29 ` Chad Carlin
1999-01-20  1:29   ` Chad Carlin
1999-01-20  2:04   ` job bogan
     [not found]     ` <job@piquin.uchicago.edu>
1999-01-20  2:28       ` Richard Offer [this message]
1999-01-20  2:36         ` Ken Klingman
1999-01-20  2:36           ` Ken Klingman
1999-01-20 21:18           ` David Watters
1999-01-20 21:18             ` David Watters
1999-01-20  3:01         ` job bogan
1999-01-20  3:01           ` job bogan
1999-01-20 21:29           ` David Watters
1999-01-20 21:29             ` David Watters
1999-01-20  3:08         ` Greg Chesson
1999-01-20  3:08           ` Greg Chesson
1999-01-20  3:32     ` Chad Carlin
1999-01-20 16:02     ` Eric Kimminau
1999-01-20 15:18 ` Eric Kimminau
1999-01-20 21:55   ` David Watters
1999-01-21  7:11   ` David S. Miller
1999-01-22 19:14     ` Jeffrey Watts

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=9901191828.ZM20761@morgaine.engr.sgi.com \
    --to=offer@morgaine.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