From: "Robert G. Brown" <rgb@phy.duke.edu>
To: ultralinux@vger.kernel.org
Subject: Re: Ultra AXmp
Date: Mon, 13 Jul 1998 13:59:33 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-90222358531024@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-90222358531013@msgid-missing>
On Sat, 11 Jul 1998, Matthew Jacob wrote:
>
>
>
> > Date: Sat, 11 Jul 1998 19:21:14 -0700 (PDT)
> > From: Matthew Jacob <mjacob@feral.com>
> >
> > Yes, but at the high end costs of CPUs are irrelevant since it
> > usually becomes storage and network infrastructure costs that
> > predominate.
> >
> > This argument sounds %100 logical and correct.
> >
> > But then why doesn't Intel just cause 4 way SMP machines to cost $20k
> > just like Sun?
> >
>
> Good question, although the answer may be "Intel is not in
> the system's business".
>
>
>
>
...and "manufacturer's who use Intel chips in 4+ CPU SMP machines have to
actually compete in an open market"....
I'm also not sure about the original premise. At the high end of
multiprocessing systems (or even at the low end:-), I would have
expected the bulk of the cost to be in the design and implementation
of the bus structure that connects the processors to enable shared
access to memory, peripherals, and each other to facilitate high speed
IPC's. Disk is cheap (especially when packaged for a standard
interface, i.e. -- SCSI UW on a PCI bus) and really NIC's (similarly
packaged) are too. Getting disk and networks onto a bus (proprietary
or otherwise) and interfaced with lots of processors and memory and
working out all the DMA issues and cache coherence issues and
busmastering issues -- that's expensive.
I thought the real claim to fame of all of Sun's multiprocessing
systems (and the SP2, and the Power Challenge, and the...) has always
been their really fast/expensive IPC bus, not their interface to
peripherals.
rgb
Robert G. Brown http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567 Fax: 919-660-2525 email:rgb@phy.duke.edu
next prev parent reply other threads:[~1998-07-13 13:59 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-11 18:36 Ultra AXmp Bob Drzyzgula
1998-07-12 1:56 ` David S. Miller
1998-07-12 2:21 ` Matthew Jacob
1998-07-12 2:29 ` David S. Miller
1998-07-12 5:02 ` Matthew Jacob
1998-07-12 12:54 ` Douglas Eadline
1998-07-12 23:59 ` Bob Drzyzgula
1998-07-13 6:27 ` Qiru Zhou
1998-07-13 6:38 ` David S. Miller
1998-07-13 10:40 ` Bob Drzyzgula
1998-07-13 12:09 ` Xavier Beaudouin
1998-07-13 13:59 ` Robert G. Brown [this message]
1998-07-13 14:29 ` Robert HYATT
1998-07-13 14:54 ` Matthew Jacob
1998-07-13 14:56 ` Matthew Jacob
1998-07-13 14:59 ` Matti Aarnio
1998-07-13 15:24 ` Robert HYATT
1998-07-13 15:38 ` Robert HYATT
1998-07-13 16:56 ` Robert G. Brown
1998-07-13 17:04 ` Robert G. Brown
1998-07-13 17:13 ` Lawrence D. Lopez
1998-07-13 17:26 ` Mike
1998-07-14 1:44 ` Shannon
1998-07-14 7:00 ` David S. Miller
1998-07-14 18:07 ` Douglas Eadline
1998-07-14 23:23 ` Bob Drzyzgula
1998-07-15 3:31 ` Dave Wreski
1998-07-15 8:07 ` Ward Deng
1998-07-15 11:14 ` Bob Drzyzgula
1998-07-15 11:27 ` David S. Miller
1998-07-15 15:54 ` Robert G. Brown
1998-07-15 17:11 ` Robert G. Brown
1998-07-15 23:22 ` Luis Ponce de Leao
1998-07-21 23:29 ` Ward Deng
1998-07-25 23:34 ` Ward Deng
1998-07-26 0:02 ` Ward Fenton
1998-07-26 0:45 ` Rich Martin
1998-07-26 3:34 ` Bob Drzyzgula
1998-07-26 4:00 ` Ward Deng
1998-07-26 4:29 ` Ward Deng
1998-07-26 12:29 ` Bob Drzyzgula
1998-07-26 13:57 ` Douglas Eadline
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=marc-linux-ultrasparc-90222358531024@msgid-missing \
--to=rgb@phy.duke.edu \
--cc=ultralinux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.