The nucleus of a multiprogramming system

Hansen, Per Brinch

doi:10.1145/362258.362278

Cited by 260 publications

(45 citation statements)

References 2 publications

(2 reference statements)

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…There have been numerous contributions that argue for a minimal operating system with policies exposed to the applications. Nucleus [4] and Exokernel [5] are two classic examples of such models. BAIO draws inspiration from these contributions and applies the principle in the restricted context of a filesystem.…”

Section: Related Workmentioning

confidence: 99%

Block Asynchronous I/O:A Flexible Infrastructure for User-Level Filesystems

Sivathanu

Venkataramani

Arpaci-Dusseau

2001

High Performance Computing — HiPC 2001

View full text Add to dashboard Cite

IntroductionKernel filesystems try to be efficient across a large variety of application requirements. This excessive generality that is inherent to the concept of an in-kernel filesystem, turns out to be a great perforamance limitation in many cases. Filesystems end up ignoring the vast knowledge available at the application level that might facilitate highly optimized policies and decisions. This huge information gap that exists between filesystems and the applciations result in generic policies being imposed on all applications uniformly, leading to sub-optimal performance. This performance impact is particularly significant in highly demanding, specialized applications like databases and web servers, Stonebraker [7] argued that inappropriate filesystem implementations can have a dramatic impact on the perforamance of databases.To achieve optimal disk I/O perforamance, it is imperative that applications have full control over all aspects of the layout and management of data on disk.Applications have the complete view of the semantics of data they manage and hence are the ideal candidates to dictate decisions on how the data is to be laid out on disk, what data is to be cached and when prefetching should occur. Potentially, applications require the power and capability to operate their own filesystem. The kernel must ideally provide a direct, protected access to the disk, and its role must be limited to regulating access to the disk by multiple processes and imposing protection boundaries. Block Asynchronous I/O (BAIO), presented in this paper, strives at achieving these objectives. This paper is organized as follows . In Section 2, we discuss about the conventional methods of doing disk I/O and their disadvantages. In section 3, we introduce BAIO and explain why BAIO is a better way of doing disk I/O compared to conventional methods. Section 4 detials the design of BAIO. Section 5 deals with implementation details. In Section 6 we provide perforamance evaluations and we discuss related work in Section 7.

show abstract

Section: Related Workmentioning

confidence: 99%

Block Asynchronous I/O:A Flexible Infrastructure for User-Level Filesystems

Sivathanu

Venkataramani

Arpaci-Dusseau

2001

High Performance Computing — HiPC 2001

View full text Add to dashboard Cite

show abstract

“…Instead, the machines are provided with "process synchronization primitives" which can be used to allow synchronization and communication between several cooperating processes which are, at least conceptually, operating asynchronously and in parallel. Among the better known of these are those of Dijkstra [1,10], Saltzer (11], and P. B. Hansen [12,13]. If all process synchronization at all levels (except the lowest which implements the primitives) to be handled in terms of the primitives, their transparency is an extremely important issue.…”

Section: An Unsolved Transparency Problem From the Operating System Areamentioning

confidence: 99%

Use of the concept of transparency in the design of hierarchically structured systems

Parnas

Siewiorek

1975

Commun. ACM

View full text Add to dashboard Cite

show abstract

“…The desired micro-kernel [6] approach for building automatic test engine (ATE) is based on analogy with operating systems [7]. In operating systems that are based on micro-kernel architecture, a very basic set of services are provided by the operating system core (e.g., process identifiers and address spaces).…”

Section: Introductionmentioning

confidence: 99%

A Micro-Kernel Test Engine for Automatic Test System

Wang¹,

Yang

2011

JCP

View full text Add to dashboard Cite

Abstract-In traditional automatic test solutions, a testengine usually encompasses all functions in its kernel, including compiling test program, generating test event chain, scheduling test process and executing test events. This makes the engine tightly coupled with test language and the system under test, so that it is difficult to maintain, optimize and extend the test engine. In order to solve these problems, a micro-kernel test engine is designed and implemented based on the service oriented architecture. This microkernel approach decouples function modules to make the test engine kernel independent of the system under test and the test language. This also makes the test engine more modularized, so that the debugging process and maintenance work of the engine can be much easier. With new compiling component and test adapters, the engine kernel can be extended for new test methods or reused in new test applications. The application example and extensibility analysis discussed in section 6 show the feasibility of this micro-kernel test engine.Index Terms-automatic test system, test engine, microkernel, service oriented architecture

show abstract

The nucleus of a multiprogramming system

Cited by 260 publications

References 2 publications

Block Asynchronous I/O:A Flexible Infrastructure for User-Level Filesystems

Block Asynchronous I/O:A Flexible Infrastructure for User-Level Filesystems

Use of the concept of transparency in the design of hierarchically structured systems

A Micro-Kernel Test Engine for Automatic Test System

Contact Info

Product

Resources

About