Xref: utzoo comp.unix.amiga:167 comp.sys.amiga.misc:592 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!samsung!umich!umeecs!msi.umn.edu!cs.umn.edu!sialis!orbit!pnet51!chucks From: chucks@pnet51.orb.mn.org (Erik Funkenbusch) Newsgroups: comp.unix.amiga,comp.sys.amiga.misc Subject: Re: Adding Symmetric Multiprocessing to Amiga UNIX. Message-ID: <4011@orbit.cts.com> Date: 5 Feb 91 10:25:01 GMT Sender: news@orbit.cts.com Organization: People-Net [pnet51], Minneapolis, MN. Lines: 41 /y xanthian@zorch.SF-Bay.ORG (Kent Paul Dolan) writes: > > dvp@sequent.com (Dan Vander Ploeg) writes: >> Marc Barrett: > >>> Although this version of UNIX does not support symmetric >>> multiprocessing as it is written, other companies -- including >>> Solbourne, Sequent, Corollary, Pyramid, Encore, ALR, and Compaq -- >>> have successfully modified older versions of AT&T UNIX System V to >>> support symmetric multiprocessing. > >> It was announced a few months ago that Sequent is working with AT&T to >> add SMP to SYS V. > >And of course, the really interesting case is not the rather imbalanced >'040/'030 pair, but the situation when several '040's are slotted in. > >There have already been successful experiments distributing graphics >processing of the sort useful for multimedia work across networked >cpu's. It would probably work a lot better to distribute similar tasks >across a fast bus with common memory, instead. Well, i just recently recieved my 68040 users manual and designers handbook from motorola, and notice some interesting things. for instance it would be quite usable to have an 040/030 pair with the 040's bus snooping capabilites. the dual mmu's in the 040 would also make it easy to protect data memory, while allowing re-entrant code to function properly. they even give complete diagrams and pal coding for an adapter board to fit into an 030 system. > >Anybody want to bring up Linda on the Amiga? ;-) > >Kent, the man from xanth. > UUCP: {amdahl!bungia, crash}!orbit!pnet51!chucks ARPA: crash!orbit!pnet51!chucks@nosc.mil INET: chucks@pnet51.orb.mn.org