All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Drzyzgula <bob@drzyzgula.org>
To: ultralinux@vger.kernel.org
Subject: Re: Ultra AXmp
Date: Wed, 15 Jul 1998 11:14:23 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-90222358531042@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-90222358531013@msgid-missing>

On Wed, Jul 15, 1998 at 02:07:05AM -0600, Ward Deng wrote:
> > 
> > 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
>                                    ^^^^^^^
> What do you mean that?

I belive that, in the case of the UltraSPARC, it would
refer to the Ultra Port Architecture (UPA), which
provides a point-to-point packet switched interconnect
for processors, memory and I/O. The UPA has special
accelerators for the cache coherancy mechanism, and
supports device connections with various bitwidths.
At over four processors, the UPA gets extended into
a more distributed architecture called the gigaplane.

Personally, I would rather that Sun had a distributed
memory machine... the UltraSPARC machines have per-CPU
cache but not per-CPU DRAM. I believe that the
UltraSPARC III specifically does provide for per-CPU
DRAM; I don't know excactly how that would be implemented
in a system architecture or OS-wise.

--Bob

See:
http://www.sun.com/microelectronics/whitepapers/wp95-023.html.
http://wwwwseast2.usec.sun.com/servers/enterprise/10000/Tour/interconnect.html
http://wwwwseast2.usec.sun.com/servers/enterprise/10000/wp/E10000.pdf


-- 
==============================
Bob Drzyzgula                             It's not a problem
bob@drzyzgula.org                until something bad happens
==============================

  parent reply	other threads:[~1998-07-15 11:14 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
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 [this message]
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-90222358531042@msgid-missing \
    --to=bob@drzyzgula.org \
    --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.