Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!think.com!mintaka!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!icdoc!jsc
From: jsc@doc.ic.ac.uk (Stephen Crane)
Newsgroups: comp.arch
Subject: Re: Historical architectural advances??
Message-ID: <2443@gould.doc.ic.ac.uk>
Date: 7 Nov 90 10:21:05 GMT
References: <1868@m1.cs.man.ac.uk> <8553@scolex.sco.COM> <1888@m1.cs.man.ac.uk>
Sender: news@doc.ic.ac.uk
Organization: Dept. of Computing, Imperial College, London, England
Lines: 18

In article <1888@m1.cs.man.ac.uk> mshute@cs.man.ac.uk (Malcolm Shute) writes:
>What is the difference between a loosely coupled multicomputer system,
>and a tightly coupled multiprocessor computer?
>
>Granularity of processes for scheduling, and geography of the 'cabinet'
>size.  That is all (just about).
Failure modes?  Tightly-coupled multiprocessors are just that and may be
assumed to fail as a single unit whereas, multicomputers exhibit partial
failure.

>
>Malcolm SHUTE.         (The AM Mollusc:   v_@_ )        Disclaimer: all

Stephen,

Stephen Crane, Department of Computing, Imperial College, 180 Queensgate, London
(SW7 2BZ) #071+[ph]5895111x5092[fax]5818024.------``To my mind, Withers, there
is no finer sight than that of a flock of kale in full flight.''"