Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!brahms.udel.edu!gdtltr
From: gdtltr@chopin.udel.edu (root@research.bdi.com (Systems Research Supervisor))
Newsgroups: comp.os.misc
Subject: Re: process migration - status and availability
Message-ID: <16939@chopin.udel.edu>
Date: 17 Apr 91 15:39:16 GMT
References: <10422@pitt.UUCP> <1991Apr14.215738.8745@news.stolaf.edu>
Organization: Brain Dead Innovations, Inc. (BDI)
Lines: 26

In article <1991Apr14.215738.8745@news.stolaf.edu> mike@sachiko.acc.stolaf.edu (Mike Haertel) writes:
=>
=>One OS I know of that could easily support migration is Amoeba; it's
=>interested to note that the current version of Amoeba supports load
=>balancing to control processor allocation at process creation time,
=>but does not have any more general migration facilities.  I suspect
=>this is a case of getting 90% of the benefits at 10% of the cost.
=>
   I believe that Amoeba supports a process checkpointing function (stun?)
for dumping process state to a file. Theoretically, this could be restarted
on another compatible processor. Amoeba avoids the problem of redirecting I/O
by making capabilities for files location-independent. Note, however, that
if a related process or file is killed/deleted while the process is being
migrated, the restarted process would most likely fail at some point.

                                        Gary Duzan
                                        Time  Lord
                                    Third Regeneration



-- 
                            gdtltr@brahms.udel.edu
   _o_                      ----------------------                        _o_
 [|o o|]   Two CPU's are better than one; N CPU's would be real nice.   [|o o|]
  |_o_|           Disclaimer: I AM Brain Dead Innovations, Inc.          |_o_|