Xref: utzoo comp.sys.ncr:515 comp.arch:18361
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!sol.ctr.columbia.edu!emory!hubcap!ncrcae!ncr-sd!se-sd!lord
From: lord@se-sd.SanDiego.NCR.COM (Dave Lord)
Newsgroups: comp.sys.ncr,comp.arch
Subject: Re: Terradata architecures
Keywords: YNet Bus
Message-ID: <3944@se-sd.SanDiego.NCR.COM>
Date: 1 Oct 90 23:39:04 GMT
References: <211@bilpin.UUCP> <1990Sep28.020717.22610@dhw68k.cts.com>
Organization: NCR Corporation, Systems Engineering - San Diego
Lines: 15

In article <1990Sep28.020717.22610@dhw68k.cts.com> stein@dhw68k.cts.com (Rick 'Transputer' Stein) writes:
:In article <211@bilpin.UUCP> nick@bilpin.UUCP (nick) writes:
:>Unfortunately he was not able to provide any real technical information.
:>
:I'd be pretty amazed to see a massively parallel computation system built
:up with busses.  That contention problem is a giant killer, and that's
:why message-passing scalar systems are kicking butt, even if they are
:a bit tougher to built software.  Shared memory systems are technological
:dinosaurs.

I don't think what you mean by bus and what they mean (Ynet Bus) are
the same thing. The Terradata archetecture is a loosely coupled message
passing system. No shared memory. Ynet is the connection along which
the messages are passed. ByNet is similar but MUCH faster. At least
that's my understanding.