Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!brl-adm!brl-sem!ron
From: ron@brl-sem.ARPA (Ron Natalie <ron>)
Newsgroups: comp.arch,misc.wanted
Subject: Re: Tightly-coupled, multi-processor UNIX systems?
Message-ID: <681@brl-sem.ARPA>
Date: Thu, 5-Mar-87 23:14:30 EST
Article-I.D.: brl-sem.681
Posted: Thu Mar  5 23:14:30 1987
Date-Received: Sat, 7-Mar-87 23:35:52 EST
References: <280@cg-d.UUCP>
Organization: Electronic Brain Research Lab
Lines: 18
Xref: mnetor comp.arch:516 misc.wanted:621

In article <280@cg-d.UUCP>, mikkel@cg-d.UUCP (Carl Mikkelsen X5220) writes:
> 
> For the last three or four years, I've heard rumors of a very
> successful multi-processor UNIX system implemented at some (sub)set of
> the following schools: {cmu,yale,purdue}.

PURDUE did a multiprocessor UNIX by replacing the SBI terminator in
their VAX 780 with another CPU.  The master processor handles most
of the kernel with time left over for user processes and user processes
are run in the slave CPU.  Gould uses most of the same code to run their
dual processor Powernode systems (as a matter of fact, Gould sucked up
a lot of the Purdue talent to do it).

Doing the Master/Slaves approach is a fairly old idea.  It was first
published in a paper from the Navy Postgraduate School in 1975.  I don't
have the reference.

-Ron