R. H. Campbell, V.Russo, and G. Johnston, "Choices: The Design of a Multiprocessor Operating System," Proceedings of the USENIX C++ Workshop,Santa Fe, November 1987.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....system that is, like Lipto, based on the object thread model [5] However, a CloutIs object is persistent and resides in its own protection domain. Consequently, Clouds objects are heavyweight and they do not support fine grained decomposi tion. Choices is an object oriented operating system [4]. It has a fine grained, modular structure based on the encapsulation, subtyping, and inheritance mechanisms of its implementation language, C . However, the entire system is contained in the kernel domain. The system s application interface is exported to user level domains using proxy objects, ....

R.H. Campbell, V. Russo, and G. Johnston. Choices: The design of a multiprocessor operating system. In Proceedings of the USENIC C++ Workshop, pages 109 123, Nov. 1987.

....effectively increase the sparseness of the address space and allow addresses to be reused. 7 Current Status The page migration and replication system is currently being designed, and a prototype will shortly be developed using the x kernel [22] We have commenced modifications of the Choices [8] operating system. A group of students are instrumenting a Unix system to obtain data for our simulations of page size, address space management and page migration. We are also building specialised network hardware which is a locally developed 110Mbps broadband ring which supports efficient ....

R. H. Campbell, V. Russo, and G. Johnston. Choices: The design of a multiprocessor operating system. In Proc. USENIX C++ W., pages 109--123, Santa Fe, USA, 1987.

....with an acceptable overhead. This chapter and the next will talk about the implementation and performance of Mungi and the protection system. 7.1 Implementation History The initial specification of Mungi was completed in early 1993. The first attempt to implement Mungi was to modify CHOICES [CRJ87] to support a single address space. CHOICES is an object oriented operating system, the strict object oriented design was intended to provide the project with a rapid prototype for Mungi. This was, unfortunately not the case, the disjoint address space model was embedded too deeply into the ....

R.H. Campbell, V. Russo, and G. Johnston. Choices: The design of a multiprocessor operating system. In USENIX C++ Workshop, pages 109--23, Santa Fe, NM, USA, 1987.

....communication 10 structure. This approach is well suited to high message rates or bursty traffic, such that the sender does not have to hold a message too long before passing it further. It has been successfully applied in operating systems which consist of several interacting components [TW97, CRJ87] A consequence of the Payloads pattern is that adding new message types does not require changing the existing entities which are not interested in them. For example, in a Data flow architecture (Section 2) filters pass downstream the messages they do not understand, without performing any ....

Roy H. Campbell, Vincent Russo, and Gary Johnston. Choices: The Design of a Multiprocessor Operating System. In Proc. USENIX C++ Workshop, pages 109--123, Santa Fe, NM, November 1987.

....and storage of such objects. It is my view that these services should be provided at the level of a language run time system or by an object support layer on top of the basic system services. This and other features distinguish Lipto from other object oriented systems, such as Choices and SOS [3, 20]. Choices is a truly object oriented operating system in that its architecture is object oriented, it exposes an object interface to applications and it is implemented using an object oriented language. Since the system is structured using the inheritance mechanism and the object model of its ....

R. H. Campbell, V. Russo, and G. Johnston. Choices: The design of a multiprocessor operating system. In Proceedings of the USENIC C++ Workshop, pages 109--123, Nov. 1987. 10

....liability of this mechanism is its inefficiency when compared with direct calls. One way to improve performance is to pack multiple messages into one container message such that all of them are transferred in one step. Although this technique has been successfully applied in operating systems [3], it is not viable for continuous media applications, where typical payloads contain time sensitive data and have large memory footprints. Optimized copying techniques see below provide better solutions. vD i s c u s s i o n Payloads are composed of two compo class IDCT: public ....

R. H. Campbell, V. Russo, and G. Johnston. Choices: The Design of a Multiprocessor Operating System. In Proc. USENIX C++ Workshop, pages 109--123, Santa Fe, NM, November 1987.

....that is, like Lipto, based on the object thread model [DLJAR91] However, a Clouds object is persistent and resides in its own protection domain. Consequently, Clouds objects are heavy weight and they do not support finegrained decomposition. Choices is an object oriented operating system [CRJ87] It has a fine grained, modular structure based on the encapsulation, subtyping, and inheritance mechanisms of its implementation language, C . However, the entire system is contained in the kernel domain. The system s application interface is exported to user level domains using proxy objects, ....

Roy H. Campbell, Vincent Russo, and Gary Johnston. Choices: The design of a multiprocessor operating system. In Proceedings of the USENIC C++ Workshop, pages 109--123, November 1987.

....used at application level and have more recently been employed as tools in the construction of operating systems [40, 65, 72] In this section we examine the features of two such operating systems, Choices and Spring. 2.4. 1 Choices Choices is an object oriented multiprocessor operating system [28] developed in the University of Illinois. It was developed on a network of Encore Multimax multiprocessors. Choices is implemented using a class hierarchical approach through C [65] The kernel is implemented as a dynamic collection of objects that have been instantiated from classes [27] ....

.... as a dynamic collection of objects that have been instantiated from classes [27] Choices provides the ability for each application to customise its own Choices operating system by choosing to include or omit different modules, and by choosing between alternative implementations of a given feature [28]. Different Choices applications running simultaneously on the same node can interact with different Choices kernels, depending on the modules that they include and omit. Choices supports an object oriented file system model [63] in which files may be mapped to virtual memory. A specialisation of ....

Roy H. Campbell, Vincent R. Russo, and Gary M. Johnston. Choices: The design of a multiprocessor operating system. In Proceedings of the USENIX C++ Workshop, 1987.

....framework of Smalltalk 80[Gol84] and the C based framework called ET [GWM89] and graphical object editors[Vli90] Frameworks can also be applied to operating system software. Choices is a family of objectoriented operating systems; it is designed as a hierarchy of frameworks[CRJ87] Besides the file system framework described in this thesis, Choices contains frameworks for the design of several other subsystems, including: virtual memory[RC89, Rus91] process scheduling and synchronization, exception handling[RJC88, Rus91] networking[ZJ90] device management[Kou91] and ....

Roy H. Campbell, Vincent Russo, and Gary Johnston. Choices: The Design of a Multiprocessor Operating System. In Proceedings of the USENIX C++ Workshop, pages 109--123, Santa Fe, New Mexico, November 1987.

....time for this simple example was about 0.0527 sec. Over 90 of the time was spent to execute CHARM kernel code, showing that the start up overhead of CHARM is very high. In order to further improve performance, we are implementing our compiler on a lower level run time system, namely, CHOICES [10], an object oriented distributed operating system, which is known to be more efficient. 4 Related work In this section, we briefly compare our work with several previous efforts to build actor based parallel languages and their compilers. Note that the first three languages, Act, Cantor and Acore, ....

Roy H. Campbell, Vincent Russo, and Gary Johnston. Choices: The Design of a Multiprocessor Operating System. In Proceedings of the USENIX C++ Workshop, pages 109--123, Santa Fe, New Mexico, November 1987. IEEE.

....A framework can be refined into subframeworks. Constraints specify the interactions between the subframeworks. We describe how we used object oriented frameworks to design Choices, an object oriented operating system. 1 Frameworks in an Object Oriented Operating System The design of Choices[1], an object oriented operating system, comprises a hierarchy of frameworks. In the design, the concept of a framework subsumes the conventional organization of an operating system into layers. Frameworks not only allow the design of layers, but they also permit the construction of more complex ....

Roy H. Campbell, Vincent Russo, and Gary Johnston. Choices: The Design of a Multiprocessor Operating System. In Proceedings of the USENIX C++ Workshop, pages 109--123, Santa Fe, New Mexico, November 1987.

....them as a force that affects packet layout. ffl Packet layout has to simplify marshalling, fragmentation, reassembly, and unmarshalling of packets. Now consider a different example of communication between system components. The virtual memory system of a modern operating system such as Choices [2] or Mach [6] consists of several interacting components. Consider the interactions for supporting memory mapped files [5] in Choices, if there is a page fault on a memory mapped file, the AddressSpace communicates with PageCaches and Files to locate the page frame, physical page, disk block, ....

Roy H. Campbell, Vincent Russo, and Gary Johnston. Choices: The Design of a Multiprocessor Operating System. In Proceedings of the USENIX C++ Workshop, pages 109--123, Santa Fe, New Mexico, November 1987.

No context found.

R. H. Campbell, V.Russo, and G. Johnston, "Choices: The Design of a Multiprocessor Operating System," Proceedings of the USENIX C++ Workshop,Santa Fe, November 1987.

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