D.L. Black, D.B. Golub, et al., "Microkernel Operating System Architecture and Mach", USENIX Micro-kernels and Other Kernel Architectures Workshop Proc., April 1992, pp. 11-30.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....(micro kernels) enforce modular design, appropriated for highly dependable systems [8, 9] and because most of current distributed operating systems are based on the microkernel concept, with classical operating system services provided by user level processes. Chorus [10] Amoeba [11] and Mach [12] are good examples of it. Even when traditional kernels are used, numerous distributed services are nevertheless implemented by user level code. In this paper, this new set of kernel services which we have called Incremental Operations after incremental checkpointing are introduced. All of ....

D.L. Black, D.B. Golub, et al., "Microkernel Operating System Architecture and Mach", USENIX Micro-kernels and Other Kernel Architectures Workshop Proc., April 1992, pp. 11-30.

....of a task. HYDRA procedures and procedure invocations are sequential in nature, while many processes may be executing concurrently. These basic object types are the basis of HYDRA s support for multiprocessor hardware, and, in turn, for an operating system built around the HYDRA kernel. Mach [3] is a microkernel developed to provide a base for other operating systems, to provide transparent access to network resources, and to exploit multiprocessor and multicomputer hardware con gurations. Mach is a microkernel, and as such separates the control of basic hardware resources from the ....

David L. Black, David B. Golub, Daniel P. Julin, Richard F. Rashid, Richard P. Draves, Randall W. Dean, Alessandro Forin, Joseph Barrera, Hideyuki Tokuda, Gerald Malan, and David Bohman. Microkernel operating system architecture and mach. In Proceedings of the USENIX Workshop on Microkernels and Other Kernel Architectures, April 1992.

....many of the issues are similar, our approach to routing messages through filters based on possibly changing message contents is much more dynamic than most of these systems. Microkernels face the similar issues to running in single or multiple address spaces as we do. Systems such as Mach [5] argued for the benefits of running modules in separate address spaces and suggested many ways to optimize IPC. The Chorus System [22] provided some flexibility as to where individual components could run. Unlike our work they were not forced to support single address space operation to run on ....

David L. Black, David B. Golub, Daniel P. Julin, Richard F. Rashid, Richard P. Draves, Randall W. Dean, Alessandro Forin, Joseph Barrera, Hideyuki Tokuda, Gerald Malan, and David Bohman. Microkernel operating system architecture and Mach. In Proceedings of the USENIX Symposium on Microkernels and Other Kernel Architectures, pages 11--30, April 1992.

.... than an implementation that requires kernel modification but it incurs higher performance overhead (Section IV) It is also possible to implement the scheme entirely in the kernel in order to minimize the overhead [22] However it is generally desirable to minimize the complexity of the kernel [8, 17]. Furthermore, the more modular approach described in this paper makes it easier to port the implementation to other kernels or other web servers. Our current implementation consists of a combination of kernel modifications and modifications to the user level web server (Figure 2) TCP IP packet ....

D. L. Black, D. B. Golub, D. P. Julin, R. F. Rashid, and R. P. Draves, "Microkernel Operating System Architecture and Mach," Proceedings of the USENIX Workshop on Micro-Kernels and Other Kernel Architectures, Berkeley, CA, pp. 11-30 (April 1992).

....of cooperating networks. Networks in a cooperating network set are spread out over a WAN. We show how sets of cooperating networks can be used to build efficient location mechanisms. 1 Introduction Because of their flexibility, microkernel based operating systems such as Chorus [Rozi87] Mach [Blac92] and Amoeba [vR92] are used to build distributed systems and in particular object oriented operating systems such as COOL [Lea93] which is built upon Chorus microkernel. Microkernels offer services which are used to build upper level environments. Internal naming facilities, location of objects, ....

D.L. Black, D.B. Golub, D.P. Julin, R.F. Rashid, R.P. Draves, R.W. Dean, A. Forin, J. Barrera, H. Tokuda, G. Malan, and D. Bohman. Microkernel Operating System Architecture and Mach. In Proc. USENIX Workshop on Micro-Kernels and Other Kernel Architectures, Seattle (USA), April 1992.

....di erentiated QoS. Additionally, processor capacity reserves do not aim at providing di erentiated QoS in clusters, nor do they provide predictable QoS in application level metrics in server systems. 5.1. 7 Migrating threads in Mach and Shuttles in Spring The migrating threads [46] of Mach [1, 23] and AlphaOS [32] and the shuttles of Spring [56] allow the resource consumption of a thread (or a shuttle) to be accounted towards the correct resource principal, when the thread (or shuttle) moves across 99 protection domains. However, a single thread cannot perform work on behalf of several ....

D. L. Black, D. B. Golub, D. P. Julin, R. F. Rashid, R. P. Draves, R. W. Dean, A. Forin, J. Barrera, H. Tokuda, G. Malan, and D. Bohman. Microkernel operating system architecture and Mach. In Workshop on Micro-Kernels and Other Kernel Architectures, pages 11-30, Seattle, WA, Apr. 1992. USENIX.

....thread policy manager thread controller interface. A detailed description of policy managers and virtual processors is given in [17, 26] 7 Physical Processors Sting is intended to serve as an operating system for modern programming languages. Like other contemporary operating systems (e.g. Mach[7, 29], Chorus[27] or Psyche[23] Sting s lowest level abstraction is a micro kernel called the Abstract Physical Machine (APM) The APM plays three important roles in the Sting software architecture: 1. It provides a secure and efficient foundation for supporting multiple virtual machines. 2. It ....

David L. Black, David B. Golub, Daniel P. Julin, Richard Rashid, Richard P. Draves, Randall W. Dean, Alessandro Forin, Joseph Barrera, Hideyuki Tokuda, Gerald Malan, and David Bohman. Microkernel Operating System Architecture and Mach. In Workshop Proceedings Micro-Kenels and other Kernel Architectures, pages 11--30, April 1992.

....notion of restricted delegation; these are often called capability based systems. Capabilities in KeyKOS, Eros, and Mach are unforgeable because the kernel manages them. A process delegates its authorization by asking the kernel to pass a capability, possibly with restriction, to another process [6, 20, 4]. Amoeba capabilities, in contrast, are secret random numbers, and may be transmitted as raw data [22, 16] Amoeba must assume that a cluster is a secure network; we consider such a cluster a single administrative domain. Snowflake end to end authorization could integrate either sort of capability ....

D. Black, D. Golub, D. Julin, R. Rashid, R. Draves, R. Dean, A. Forin, J. Barrera, H. Tokuda, G. Malan, and D. Bohman. Microkernel operating system architecture and Mach. In Proceedings of the USENIX Workshop on Micro-Kernels and Other Kernel Architectures, pages 11--31, 1992.

....and the device drivers. Other functionality can be implemented in one or more servers that are run by the kernel as regular user programs. 2.2.1 UX Server The UX server is a user program that contains the 4.3 BSD UNIX code that was removed from the kernel when Mach 2.5 was turned into Mach 3. 0 [2]. It attempts to exploit parallelism by being multithreaded. The UX server depends on a system call emulator that is mapped into the address space of every user program. Mach 3.0 provides a system call interface, but it handles system calls that are specific to Mach, such as send and receive ....

David L. Black, David B. Golub, Daniel P. Julin, Richard F. Rashid, et al., "Microkernel Operating System Architecture and Mach", USENIX Micro-kernels and Other Kernel Architectures workshop, 1992.

....(Black, 1990) Kernel handoff scheduling however caused problems for Duchamp (1991) implementing a transaction manager on Mach 2, causing the creation of 25 to 35 threads when 1 thread only was needed. 26 Mach 3. 0 also uses continuations for IPC, exception handling and page fault handling (Black et al. 1992). 27 Each thread has a relative priority within its actor. However scheduling is based on the absolute priority which is the sum of actor priority and thread relative priority. distributed shared virtual memory in these systems. Multiple servers can run simultaneously and provide various ....

....New work on Mach has been to decompose this single server approach into finer grain, more general servers which can be composed together to give various functionalities. The aim of this work is to have inter changeable components, code reuse through object oriented techniques, and portability (Black et al. 1992). These fine grain servers are presumably based on Mach tasks, accessed, as in the single server case, via an emulation library. 6 Language paradigm specific Whereas the kernels in the preceding section were mainly concerned with conventionallevel operating system support, some kernels are ....

Black, D., D.B. Golub, D.P. Julin, R.F. Rashid, R.P. Draves, R.W. Dean, A. Forin, J. Barrera, H. Tokuda, G. Malan and D. Bohman (1992) Microkernel operating system architecture and Mach. Proc. Usenix Workshop on Microkernels and Other Kernel Architectures (April), 11-30.

....relieving the application programmer and language implementor of the burden of writing lowlevel routines. An alternative mechanism is to access system services via inter process communication to a server process, as seen in the microkernel architectures. In the proxy objects described by Black et al. 1992) server code is loaded into the client application address space. This converges with the other approach to the reuse of operating system code; that is, linking to specific routines which include code necessary only for the application. This direct linking approach is seen in language systems ....

Microkernel operating system architecture and Mach. Proc. Usenix Workshop on Microkernels and Other Kernel Architectures

....can also be large because each abstraction must be supported behind the trap interface. In a microkernel system, much of the policy is moved out of the kernel and into CHAPTER 1. INTRODUCTION 17 user level servers. Examples of microkernel systems include Amoeba (Tanenbaum et al. 1990) Mach (Black et al. 1992) and Chorus (Rozier et al. 1988) Placing policy in user level servers allows resource management policies to be altered by changing servers. In this sense, microkernel operating systems can be thought of as customisable. In general, customisation is achieved at either the kernel or user level. ....

....CM 5 (LoVerso et al. 1993) CHAPTER 2. PERSISTENT STORE DESIGN 43 2.4.9 Single Level Store An alternative to providing a kernel based file system is to map both primary and secondary storage into virtual memory, thus creating a single level store. This approach was used in the design of Mach (Black et al. 1992). Golub et al. 1990) showed how a conventional file system could be implemented upon such a system. An emulation library maps the file into the processes address space on an open system call. Read, write and lseek system calls are then emulated by the library. Although it simplifies the kernel ....

[Article contains additional citation context not shown here]

Black, D.L., Golub, D.B., Julin, D.P., Rashid, F.R., Draves, R.P., Dean, D.W., Forin, A., Barrera, J., Tokuda, H., Malan, G., & Bohman, D. 1992. Microkernel Operating System Architecture and Mach. Pages 11--30 of: Proceedings REFERENCES 132 of the USENIX Workshop on Micro-Kernel and Other Kernel Architectures.

....have generally followed one of two approaches. The first is to separate an existing operating system kernel into a microkernel that provides a basic set of fundamental constructs and one or more user level server tasks which run on top of the microkernel and provide operating system services [Black et al. 92] Rosier at al. 92] This approach has been applied to a number of commercial operating systems [Batlivala et al. 92] Borgendale at al. 94] Golub et al. 90] Golub et al. 93] Malan et al. 90] Phelan et al. 93] Weicek et al. 93] The second approach is to design an entirely new operating ....

Black, D. et al. "Microkernel Operating System Architecture and Mach." In Proceedings of the USENIX Workshop on Micro-Kernels and Other Kernel Architectures (Seattle, WA. April 27, 28). The USENIX Association, Berkeley, CA, 1992, pp. 11-30.

....univerities: University of California at Berkeley and Carnegie Mellon University (CMU) in Pittsburgh. Starting in 1978 Berkeley was developing Unix that was originally started at Bell Laboratories in 1969 descending from CTSS [11] and Multics [23] Carnegie Mellon University was developing Mach [1, 3, 26, 8], which took a lot of heritage from Berkeley Unix [18] and Accent [27] a research operating system from CMU. In 1989 Mach was split into two: a microkernel providing a limited number of well defined abstractions and user level servers providing other functionality such as filesystems. 1.1.1 Unix ....

David Black, David Golub, Daniel Julin, Richard Rashid, Richard Draves, Randall Dean, Alessandro Forin, Joseph Barrera, Hideyuki Tokuda, Gerald Malan, and David Bohman. Microkernel Operating System Architecture and Mach. In Micro-kernels and Other Kernel Architectures, pages 11--30, Seattle, April 1992. Usenix.

....from the Sprite kernel with equivalent Mach based code. The second step was to replace system call stubs in Sprite s C runtime library with emulation routines that make Matchmaker RPC requests to the Sprite server. These steps are similar to the transformation that was used to port UNIX to Mach [3, 9]. 3 The result is the system shown in Figure 1. User processes communicate with the Sprite server using Matchmaker RPCs, which use Mach interprocess communication (IPC) as a transport. The emulation code in each process can also make direct kernel requests (e.g. to allocate scratch memory) ....

David L. Black et al. "Microkernel Operating System Architecture and Mach", Proceedings of the USENIX Microkernel Workshop, April 1992, 11--29.

.... obtain operating system services from the personality (though the services of the microkernel might be used to provide communication between the applications and the personality) Two microkernels that have achieved some degree of success are Chorus [7] from Chorus Systems, and Mach [4], from Carnegie Mellon University. Both have been used as the basis of UNIX implementations: Chorus with UNIX System V Release 4 [1] and Mach with Berkeley UNIX and OSF 1 [5] There have been a few experiments in building personalities for other operating systems on top of Mach [6, 9] IBM has ....

R. Draves et al., Microkernel Operating System Architecture and Mach, in Proceedings of the Usenix Workshop on Micro-kernels and Other Kernel Architectures, April '92.

....performance under different circumstances. Thus it is important to provide operating system facilities that are appropriate to the application. Micro kernels have addressed this problem by providing a minimal kernel, and encapsulating the rest of OS functionality in replaceable server processes [4, 5, 9, 10, 15, 22, 27]. Such systems can be customized by replacing or providing additional servers that implement the desired policies while making use of existing mechanisms provided by the micro kernel. Using this approach, customization is supported at a coarse granularity, through the replacement of complete ....

D.L. Black, D.B. Golub, D.P. Julin, R.F. Rashid, R.P. Draves, R.W. Dean, A. Forin, J. Barrera, H. Tokuda, G. Malan, and D. Bohman. Microkernel Operating System Architecture and Mach. In Proceedings of the Workshop on Micro-Kernels and Other Kernel Architectures, pages 11--30, Seattle, WA, April 1992.

....this section differ in that migration is handled by modules residing in system space but not for the most part within the kernel itself as was the case with Amoeba and V, described in section 3. 4. 1 Task migration over Mach Task migration and load distribution support has been added to the Mach [32] microkernel by Milojici c, Zint, Dangel and Giese at Kaiserslautern. Their aim was to provide transparent and portable migration in user space with minimal kernel level modifications. The system was implemented on three i486 PCs linked via Ethernet, running Mach NORMA (NO Remote Memory Access) ....

D. L. Black. Microkernel operating system architecture and Mach. In USENIX Workshop Proceedings --- Microkernels and Other Kernel Architectures, pages 11--30, Seattle, Washington, April 1992.

....kernel abstraction to propose a suitable structure for configurable and adaptive operating system kernels for multiprocessors. More generally, this research contributes to two current research streams, one addressing the structure of and facilities provided by operating system microkernels [12, 45], the other addressing the representation and description of object oriented operating systems to facilitate changes in their implementation without affecting the application programs using them[14, 47] Our contribution to these research streams is the exploration of runtime configurability in ....

....to tailor operating system abstractions to suit the requirements of particular application programs 5 . As a result, existing micro kernel based operating systems support only coarse grain dynamic configuration, such as the dynamic replacement of specific operating system servers possible in MACH[12] and CHORUS[45] This section addresses the generalization of the model of configurable locks presented in this paper toward the configuration of arbitrary kernel level operating system abstractions. Our expectation is that operating system abstractions implemented in a manner similar to adaptive ....

Black, D., Golub, D., Julin, D., Rashid, R., Draves, R., Dean, R., Forin, A., Barrera, J., Tokuda, H., Malan, G., and Bohman, D. Microkernel operating system architectures and Mach. In Proceedings of the USENIX Workshop on Micro-Kernels and Other Kernel Architectures (April 1992), pp. 11--30.

....of the operating system inside the kernel, thereby potentially improving operating system portability. Furthermore, the use of common underlying services provides support for the coexistence and interoperability of multiple operating system environments on a single host as user level programs [32]. Mach [32] Chorus [197] KeyKOS [42] QNX [106] and BirLiX [208] are a few examples of micro kernel based operating systems. 2.8 Application specific Operating Systems Many application domains impose specific requirements on operating system functionality, performance, and structure. One ....

....operating system inside the kernel, thereby potentially improving operating system portability. Furthermore, the use of common underlying services provides support for the coexistence and interoperability of multiple operating system environments on a single host as user level programs [32] Mach [32], Chorus [197] KeyKOS [42] QNX [106] and BirLiX [208] are a few examples of micro kernel based operating systems. 2.8 Application specific Operating Systems Many application domains impose specific requirements on operating system functionality, performance, and structure. One blatant example ....

[Article contains additional citation context not shown here]

D. Black, D. Golub, D. Julin, R. Rashid, R. Draves, R. Dean, A. Forin, J. Barrera, H. Tokuda, G. Malan, and D. Bohman. Microkernel operating system architectures and mach. In Proceedings of the USENIX Workshop on Micro-Kernels and Other Kernel Architectures, pages 11--30, April 1992.

....breaking a complex system into pieces, the complexity becomes more manageable. Address spaces provide security by installing firewalls between applications. These two issues are orthogonal, but the distinction has been lost in systems research that has been concentrating on so called microkernels [Black92, Cheriton94, Engler95, Hildebrand92, Julin91, Young89]. Liedtke95] argues that microkernels have failed exclusively on performance grounds, and that poor performance is their only cause for inflexibility. Our argument is the opposite: inflexibility is inherent in the design, and leads to unavoidable inefficiencies that can only be mitigated by good ....

David Black, David Golub, Daniel Julin, Richard Rashid, Richard Draves, Randall Dean, Alessandro Forin, Joseph Barrera, Hideyuki Tokuda, Gerald Malan, David Bohman. Microkernel Operating System Architecture and Mach. In 1 st USENIX Workshop on Micro-kernels and Other Kernel Architectures, pages 11-30, Seattle, April 1992.

....application specified policy to the kernel. The success of this approach depends on the ability to anticipate appropriate policies for future applications. Micro kernel operating systems take an alternative approach by encapsulating some operating system functionality in application level servers [3, 13, 14, 19, 22]. The interfaces within such operating systems are implemented using message passing facilities provided by the micro kernel. These systems can be customized by providing additional or replacement servers that implement the desired policies while making use of existing mechanisms provided by the ....

D.L. Black, D.B. Golub, D.P. Julin, R.F. Rashid, R.P. Draves, R.W. Dean, A. Forin, J. Barrera, H. Tokuda, G. Malan, and D. Bohman. Microkernel Operating System Architecture and Mach. In Proceedings of the Workshop on Micro-Kernels and Other Kernel Architectures, pages 11--30, Seattle, WA, April 1992.

No context found.

D.L. Black, D.B. Golub, D.P. Julin, R.F. Rashid, R.P. Draves, R.W. Dean, A. Forin, J. Barrera, H. Tokuda, G. Malan, and D. Bohman. Microkernel operating system architecture and mach. In Proceedings of the USENIX Workshop on Micro-Kernels and Other Kernel Architectures, pages 11--31, 1992.

No context found.

Black, D. L., Golub, D. B., Julin, D. P., Rashid, R. F., Draves, R. P., Dean, R. W., Forin, A., Barrera, J., Tokuda, H., Malan, G. and Bohman, D. Microkernel operating system architecture and mach. In Proceedings of the Micro-kernels and Other Kernel Architectures Workshop, Seattle, Washington, USENIX, 1130, 1992.

No context found.

D. L. Black et al. Microkernel Operating System Architecture and Mach. In Proceedings of the Workshop on Micro-kernels and Other Kernel Architectures, pages 11-- 30, April 1992.

First 50 documents

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