🚀 go-pugleaf

In article <13445@dog.ee.lbl.gov> torek@elf.ee.lbl.gov (Chris Torek) writes:
=>Why not just build a multiprocessor system with completely different
=>processors?  I.e., ship a system that contains, say, one 68040 and one
=>or more 88x00s.  There is no particular reason that the O/S cannot run
=>the proper binary on the proper CPU automatically.

   There was a paper on something like this in Operating Systems Review
about a year ago. The system was called AAMP (I think) and was written
by someone from Sequent. The system arranged resource management in a
heirarchical structure, with the root actually managing memory and I/O.
Client operating systems perform basic I/O functions by passing messages
to its immediate server, and on up the tree. A server has access to the
memory spaces of its clients, which facilitates message passing and
allows for easy debugging of client operating systems.
   The example system was a Sequent Symmetry running several copies of
a modified Dynix but the paper made its point that a heterogeneous,
multi-OS multiprocessor is possible.

                                        Gary Duzan
                                        Time  Lord
                                    Third Regeneration



-- 
                            gdtltr@brahms.udel.edu
   _o_                      ----------------------                        _o_
 [|o o|]                   To be is to be networked.                    [|o o|]
  |_o_|        Disclaimer: I have no idea what I am talking about.       |_o_|