Xref: utzoo comp.sys.amiga.tech:15659 comp.sys.amiga.hardware:4371
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!sol.ctr.columbia.edu!caen!gilgalad
From: gilgalad@caen.engin.umich.edu (Ralph Seguin)
Newsgroups: comp.sys.amiga.tech,comp.sys.amiga.hardware
Subject: RISC Amiga and multiprocessing
Message-ID: <1990Nov2.070729.19128@engin.umich.edu>
Date: 2 Nov 90 07:07:29 GMT
Sender: news@engin.umich.edu (CAEN Netnews)
Distribution: na
Organization: University of Michigan Engineering, Ann Arbor
Lines: 25

With all this talk of plopping RISC boards into your Amiga, I've had a
question that's been nagging me:  Is that beautiful piece of code we
call Exec going to allow for scheduling, recognition, ..., on 
multiple processors (of different sorts)?  Symmetric MultiProcessing (oooh,
nice buzzword 8-)?  It would really be nice to have Exec worry about
what is to be executed where.  Have your Amiga with an ethernet board,
and an i860 board (with 8 processors of course 8-), an 88000 board,
and a MIPS R3000 board, and you have a serious compute server.  Machines
will be doing RPCs to your machine left and right.  Thus we have the need
for ..., yep you guessed it, FDDI.  I asked this before, but is anybody
working on an FDDI board for the Amiga?  Granted an 030 could not produce
data fast enough to fill that kind of bandwidth, but we're not going
to be sticking with 030 for long...8-)

Hey Amiga crew, how about it?  FDDI in the 4000, as well as ethernet
and Token Ring (Don't care too much for Token myself).  OS people,
let's have support for a heterogeneous network of processors, and
transparent scheduling, etc.

			Thanks, Ralph


Ralph Seguin			gilgalad@dip.eecs.umich.edu
536 South Forest Apt. #915	gilgalad@caen.engin.umich.edu
Ann Arbor, MI 48104		(313) 662-4805