tailieunhanh - The Pebble Component-Based Operating System

One way in which agencies work together is by adopting a program known as local mutual aid. This program allows neighboring communities to pool resources and share liability for damages or loss of equipment. If one community needs a particular piece of equipment, it may borrow it from a neighboring community. The equipment will become an asset of the borrowing community and will be covered under their insurance until it is released and returns to its home organization. It is important that those involved in planning the event know the agreements established between neighboring communities and. | USENIX THE ADVANCED COMPUTING SYSTEMS ASSOCIATION The following paper was originally published in the Proceedings of the USENIX Annual Technical Conference Monterey California USA June 6-11 1999 The Pebble Component-Based Operating System Eran Gabber Christopher Small John Bruno José Brustoloni and Avi Silberschatz Lucent Technologies Bell Laboratories 1999 by The USENIX Association All Rights Reserved Rights to individual papers remain with the author or the author s employer. Permission is granted for noncommercial reproduction of the work for educational or research purposes. This copyright notice must be included in the reproduced paper. USENIX acknowledges all trademarks herein. For more information about the USENIX Association Phone 1 510 528 8649 FAX 1 510 548 5738 Email office@ WWW http The Pebble Component-Based Operating System Eran Gabber Christopher Small John Bruno . José Brustoloni and Avi Silberschatz Information Sciences Research Center Lucent Technologies Bell Laboratories 600 Mountain Ave. Murray Hill NJ 07974 eran chris jbruno jcb avi @ Also affiliated with the University of California at Santa Barbara Abstract Pebble is a new operating system designed with the goals of flexibility safety and performance. Its architecture combines a set of features heretofore not found in a single system including a a minimal privileged mode nucleus responsible for switching between protection domains b implementation of all system services by replaceable user-level components with minimal privileges including the scheduler and all device drivers that run in separate protection domains enforced by hardware memory protection and c generation of code specialized for each possible cross-domain transfer. The combination of these techniques results in a system with extremely inexpensive cross-domain calls that makes it well-suited for both efficiently specializing the operating system on a per-application basis and .