M. O'Connor, B. Tangney, V. Cahill and N. Harris, "Microkernel Support for Migration". Distributed Systems Engineering Journal. 1993.  Home/Search   Document Details and Download   Summary   Related Articles   Check

.... none of the three microkernel implementations of which we are aware are completely satisfactory. The Mach implementation [17] like ours, aborts threads in kernel state and in addition leaves residual dependencies on the source host when migrating a Unix process. The implementation for Chorus [16] deals with system calls by waiting for them to complete. In the case of Amoeba, we believe a complete implementation is feasible, but requires more resources than we had available for this work. 3 More generally, our experience shows once again the effort required as outsiders to make a ....

M. O'Connor, B. Tangney, V. Cahill and N. Harris, "Microkernel Support for Migration". Distributed Systems Engineering Journal. 1993.

....(domain = within one communication domain, interdomain = across two different communication domains) Note that the COR results in the graph are where one text and data page are migrated. A number of researchers have reported on the time taken to migrate a 100 kilobyte singlethreaded user process [1, 12, 14]. Thus, in Table 5.1, we present our measurements for migrating a 100 Kilobyte process. The studied methods have their advantages and disadvantages. The advantage of the Copy Table 5.1 Migration Method Communication Domain Time to migrate 100K process Standard deviation Copy On Reference ....

M. O'Connor, B. Tangney, V. Cahill and N. Harris. Micro-kernel Support for Migration. Technical Report TCD-CS-94-43. Trinity College, Dublin, Ireland, 1994.

....message passing based distributed operating system that utilises a microkernel. A process is Chorus is called an actor. An actor can have multiple threads of execution, and utilises ports and messages to allow processes to communicate with each other [Rozier et al. 92] The Amadeus Project [O Connor et al. 94] follows with Chorus object oriented flavour, hence process (actor) migration on Chorus, is performed by three modules: kernel, transport and policy. The kernel module is responsible for encapsulating the state information of migrating processes and for re establishing these processes on other ....

....systems with process migration support to identify our approach s soundness and feasibility. The following section details the type of process environment on each system, and the steps the migration facilities take. In Chorus, to migrate a process (on a network of Micro Vax IIs) takes [O Connor et al. 94] 200 8 a 120 b milliseconds where a equals the number of kilobytes to be flushed at the source node of the migration, and b is the number of these pages later referenced by the actor. To migrate a task in the Mach operating system (on a 33 MHz i80486 PC) takes [Milojicic 94a] SMS time 150 ....

[Article contains additional citation context not shown here]

M. O'Connor, B. Tangney, V. Cahill and N. Harris. Micro-kernel Support for Migration. Technical Report TCD-CS-94-43. Trinity College, Dublin, Ireland.

....objects. 3 Process Migration Process migration has been the subject of a considerable amount of research, and there have been a number of implementations reported in the literature, both for distributed operating systems, eg [Theimer et al. 1985; Douglis and Ousterhout, 1991; Thiel, 1991; O Connor et al. 1993; Milojicic, 1994] and for Unix, eg [Litzkow and Solomon, 1992; Barak et al. 1996] Motivations for process migration include load balancing, and locality the ability of a process to move to the same host as some resource or user. Our main interest in process migration is to assess ....

....three microkernel implementations of which we are aware are completely satisfactory. The Mach implementation [Milojicic, 1994] like ours, aborts threads in kernel state and in addition leaves residual dependencies on the source host when migrating a Unix process. The implementation for Chorus [O Connor et al. 1993] deals with system calls by waiting for them to complete. In the case of Amoeba, a complete implementation should be feasible, but requires more resources than we had available for this work. Acknowledgments We are grateful for the assistance of Andrew Tanenbaum and the members of the Amoeba ....

O'Connor, M. et al. (1993). Microkernel Support for Migration. Distributed Systems Engineering Journal.

....state grouped in a single place, reliable ordered communication service and multi cast communication service. To those, we add the concept of reliable ports. More work has to be done in order to support more realistic processes using signals, file and terminal connections. For instance, in [O Co94], the authors wrote a terminal server to buffer all data sent between actors and their associated terminals. 6 Limitations and extensions Chorus offers distributed system developers key tools for distribution (modularity of global systems, performing communications, transparent localization of ....

M. O'Connor, B. Tangney, V. Cahill, and N. Harris. Micro-kernel Support for Migration. Distributed Systems Engineering Journal, 1(4), June 1994.

....dependency is limited to the possible scattering of an application s memory pages around the cluster as a result of frequent migrations. Both the Chorus and Mach systems demonstrate the suitability of microkernel based operating systems for the incorporation of migration subsystems. References: [39] 5 Systems Providing Object Migration The systems mentioned so far all provide support for process or task migration. Those mentioned in this section offer support for rather more abstract object migration, at varying levels of granularity. A common problem with such systems is that of ....

M. O'Connor, B. Tangney, V. Cahill, and N. Harris. Microkernel support for migration. Distributed Systems Engineering Journal, 1(4):212--223, June 1994.

....[BW88] Nest [Ezz86] Rhodos [ZGG90] Sprite [OCD 88] Syst eme V [Che88] mais une mise en oeuvre efficace est rarement obtenue. L impl ementation d un tel m ecanisme est moins complexe dans un syst eme con cu suivant la technologie micro noyau (Mach [ABB 86] Chorus [Roz92] CTCH94] MZDG93] que dans les syst emes monolithiques (UNIX, AK88] Une revue des diff erentes implantations peut etre trouv ee dans [JV89] Smi88] Une comparaison des performances des diff erentes impl ementations est difficile puisque chacune utilise un support mat eriel et des benchmarks ....

M. Connor, B. Tangney, V. Cahill, and N. Harris. Micro-kernel support for migration. Distributed System Engineering, 1:212--223, 1994.

....by most operating systems and is therefore considered trivial. However, a process may already be suspended at migration time as result of a kernel trap. The process might be waiting for disk I O to complete or arrival of a message. This poses a problem. One solution adopted by the Amadeus project [OTCH94] and Xcode system [Zic86] is simply to wait for the system call to complete. Amadeus was an implementation of a process migration mechanism build on top of Chorus [BL91] Since most system calls in Chorus return within a few microseconds, this delay is not serious. However, most systems have ....

....CHAPTER 2. SURVEY OF RELEVANT WORK 21 processor with no residential pages. As page faults occur, they are paged in from the file server in the usual manner. This approach, called lazy copying, is used in the Sprite operating system [DO87] and a similar approach is used in the Amadeus project [OTCH94] It only requires the availability of the node(s) which handle the virtual memory system. The drawback is that all memory pages need to be transferred over the network twice. Once to flush them to disk, and then once again, when a page fault occurs at the destination host. Resuming execution ....

M. O'Conner, B. Tangney, V. Cahill, and N. Harris. Amadeus Project, Micro--kernel Support for Migration. Document # TCDCS -94-43, Dept. of Computer Science, University of Dublin, Ireland, 1994.

....use of a preprocessor that annotates the application with the necessary statement labels and goto calls. Aside from these software systems, support for adaptive execution on a shared environment is also available from systems such as Sprite [21, 22] Mosix [23, 24] V [25] Mach [26] and Chorus [27]. The difference between these systems from MMPVM and those mentioned previously is that these systems are implemented at the operating system level. While these systems can handle most of the problems associated with user level implementations (e.g. total migration transparency and efficient ....

M. O'Connor, B. Tangney, V. Cahill, and N. Harris. Microkernel support for migration. Submitted to Distributed Systems Engineering Journal, December 1993.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC