The CHORUS Distributed Operating System: Some Design Issues

Rozier, Marc; Martins, J. Legatheaux

doi:10.1007/978-3-642-46604-5_10

Cited by 80 publications

(59 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It was to be replaced by a new implementation termed "JavaOS for Business" that also ran only Java applications. "JavaOS for Consumers" is built on the Chorus microkernel OS [31] to achieve real-time properties needed in embedded systems. Both of these systems apparently require a separate JVM for each Java application, and all run in supervisor mode.…”

Section: Java Extensionsmentioning

confidence: 99%

Processes in KaffeOS: Isolation, Resource Management, and Sharing in Java

Back¹,

Hsieh²,

Lepreau³

2000

View full text Add to dashboard Cite

Single-language runtime systems, in the form of Java virtual machines, are widely deployed platforms for executing untrusted mobile code. These runtimes provide some of the features that operating systems provide: inter-application memory protection and basic system services. They do not, however, provide the ability to isolate applications from each other, or limit their resource consumption. This paper describes KaffeOS, a system that provides these features for a Java runtime. The KaffeOS architecture takes many lessons from operating system design, such as the use of a user/kernel boundary.The KaffeOS architecture supports the OS abstraction of a process in a Java virtual machine. Each process executes as if it were run in its own virtual machine, including separate garbage collection of its own heap. The difficulty in designing KaffeOS lay in balancing the goals of isolation and resource management against the goal of allowing direct sharing. Overall, KaffeOS is up to 11% slower than the freely available JVM on which it is based, which is an acceptable penalty for the safety that it provides. KaffeOS is substantially slower than commercial JVMs, but exhibits much better performance scaling in the presence of uncooperative code.

show abstract

Section: Java Extensionsmentioning

confidence: 99%

Processes in KaffeOS: Isolation, Resource Management, and Sharing in Java

Back¹,

Hsieh²,

Lepreau³

2000

View full text Add to dashboard Cite

show abstract

“…Our threads, however, are stronger than those in TAM [7] and in some user-level threads packages, e.g. Chorus [21], which require that the maximum stack size be specified upon thread creation so that memory can be preallocated. and data are transferred to the child and the call is made on the parent stack.…”

Section: Overviewmentioning

confidence: 99%

“…Attempts to accommodate logical parallelism have include thread packages [8,21,6], compiler techniques and clever run-time representations [7,19,16,25,23,20,10], and direct hardware support for fine-grained parallel execution [13,2]. These approaches have been used to implement many parallel languages, e.g.…”

Section: Related Workmentioning

confidence: 99%

Enabling Primitives for Compiling Parallel Languages

Goldstein

Schauser

Culler

1996

Languages, Compilers and Run-Time Systems for Scalable Computers

View full text Add to dashboard Cite

This paper presents three novel language implementation primitives-lazy threads, stacklets, and synchronizers-and shows how they combine to provide a parallel call at nearly the efficiency of a sequential call. The central idea is to transform parallel calls into parallel-ready sequential calls. Excess parallelism degrades into sequential calls with the attendant efficient stack management and direct transfer of control and data, unless a call truly needs to execute in parallel, in which case it gets its own thread of control. We show how these techniques can be applied to distribute work efficiently on multiprocessors.

show abstract

“…Micro-kernel operating systems 5,6,11,9,21,27,29] were an early example of this trend, and improve adaptiveness by a l l o wing operating system functionality to be implemented in user-level servers that can be customized and con gured to produce specialpurpose operating systems. While micro-kernel-based architectures improve adaptiveness over monolithic kernels, support for user-level servers incurs a high performance penalty.…”

Section: Related Workmentioning

confidence: 99%

Optimistic incremental specialization

Autrey

Black

et al. 1995

SIGOPS Oper. Syst. Rev.

View full text Add to dashboard Cite

Conventional operating system code is written to deal with all possible system states, and performs considerable interpretation to determine the current system state before taking action. A consequence of this approach i s t h a t k ernel calls which perform little actual work take a long time to execute. To address this problem, we use specialized operating system code that reduces interpretation for common cases, but still behaves correctly in the fully general case. We describe how specialized operating system code can be generated and bound incrementally as the information on which it depends becomes available. We extend our specialization techniques to include the notion of optimistic incremental specialization: a technique for generating specialized kernel code optimistically for system states that are likely to occur, but not certain. The ideas outlined in this paper allow the conventional kernel design tenet of \optimizing for the common case" to be extended to the domain of adaptive operating systems. We also show that aggressive u s e o f specialization can produce in-kernel implementations of operating system functionality with performance comparable to user-level implementations.We demonstrate that these ideas are applicable in realworld operating systems by describing a re-implementation of the HP-UX le system. Our specialized read system call reduces the cost of a single byte read by a factor of 3, and an 8 KB read by 26%, while preserving the semantics of the HP-UX read call. By relaxing the semantics of HP-UX read we w ere able to cut the cost of a single byte read system call by more than an order of magnitude.

show abstract

The CHORUS Distributed Operating System: Some Design Issues

Cited by 80 publications

References 7 publications

Processes in KaffeOS: Isolation, Resource Management, and Sharing in Java

Processes in KaffeOS: Isolation, Resource Management, and Sharing in Java

Enabling Primitives for Compiling Parallel Languages

Optimistic incremental specialization

Contact Info

Product

Resources

About