B. Ford, G. Back, G. Benson, J. Lepreau, A. Lin, and O. Shivers. The Flux OSKit: A substrate for OS and language research. In 16th ACM Symposium on Operating System Principles, October 1997.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....accepts active packets that can initiate the execution of packet specific code. Each related code base and flow of active packets is known as an active application. During the course of the Active Networks research program, funded by DARPA, researchers developed a number of node operating systems [4 7], execution environments [8 12] and active applications [ 13 19] While innovative and radical when considered for use inside networks, active network execution environments share much in common with virtual machines used in Internet based software architectures, and active applications appear ....

B. Ford, G. Back, G. Benson, J. Lepreau, A. Lin and O. Shivers, "The Flux OSKit: A Substrate for OS and Language Research", Proceedings of the 16th ACM Symposium on Operating Systems Principles, ACM Press, October 1997.

....or unnecessary synchronization points in component based systems software. Further, we show that TSL can realistically be applied to large, complex systems. 1. Introduction Component based systems software, as exemplified by systems such as Koala [20] Click [12] TinyOS [10] and the OSKit [5], is motivated by a number of requirements: short time to market, evolvability to meet changing needs, long term software reuse, and small memory footprint in delivered systems. Another requirement of systems software, high dependability, is potentially undermined both by the diversity of ....

....data from the Monitor component and sends it out on the network using the TCP IP and Ethernet components. All components make use of a memory allocator. For simplicity we have omitted many infrastructure components: building a system like this with an operating system kit such as the OSKit [5] requires an order of magnitude more components. The component interconnections are of two types: explicit and implicit. Explicit connections are due to a component importing an interface provided by another component; the connection from TCP IP to Ethernet is of this form. Implicit connections ....

[Article contains additional citation context not shown here]

B. Ford, G. Back, G. Benson, J. Lepreau, A. Lin, and O. Shivers. The Flux OSKit: A substrate for OS and language research. In Proc. of the 16th ACM Symposium on Operating Systems Principles, pages 38--51, Oct. 1997.

....functionality, or to implement additional functionality in an existing system. Building customizable operating systems using open implementations has been an active area of research in the last decade. Examples of such customizable operating systems include SPIN [6] Exokernel [16] the Flux OSKit [18], Vino [52] SLIC [21] Choices [7] and Apertos [64] In customizable operating systems correctness depends on extensions not being able to affect parts of the system beyond the extension s scope. SPIN provides such protection through the use of a type safe programming language combined with a ....

Ford, B., G. Back, G. Benson, J. Lepreau, A. Lin, and O. Shivers. The Flux OSKit: A Substrate for OS and Language Research. in 16th ACM Symposium on Operating System Principles. 1997. Saint-Malo, France.

....application modifications, Alpine cannot achieve the high performance of many of these systems. 3. Simplified development. Work has also been done to make kernel development easier. For example, 12] redesigned the kernel from scratch to allow user and kernel modules to be interchanged. Likewise, [17] simplifies development by separating the operating system kernel into encapsulated components, which can be interchanged or reused. In contrast, we have developed Alpine for an unmodified legacy operating system with unmodified application binaries. T #r#8hy# T pxr# U8Q DQ ....

B. Ford, G. Back, G. Benson, J. Lepreau, A. Lin, and O. Shivers. The flux oskit: A substrate for os and language research. In 16th ACM Symposium on Operating Systems Principles, October 1997.

....Its objective is to facilitate migration from one platform to another. Only the implementation of this hardware abstraction layer needs to be modified. For our initial platform (a PC) some of the functions of this hardware abstract interface come from a publicly available toolset called OSKit [1], which is intended to ease the low level aspects of the development of an operating system. They are written in assembly and C language. We also use the facilities of OSKit for booting the application from a diskette or from the net. The kernel is directly usable as the basis for the gnat ....

Ford, B., G. Back, G. Benson, J. Lepreau, A. Lin, and O. Shivers. (1997). The Flux OSKit: a Substrate for OS and Language Research. Proceedings of the 16th ACM Symposium on Operating Systems Principles, Saint Malo, France (http://www.cs.utah.edu/flux/oskit)

.... requirements constraints [2] and extending semantic analysis on variants of components to the pre deployment phase [12] Similar ideas have been pursued in current microkernel operating systems research, where components embody operating system services and can be dynamically changed (e.g. [13, 30]) This work tends to be less abstract and more concerned about performance. Self Checking Systems Self checking systems employ a type of run time specification checking, where formal assertions about the state of the software or the values of inputs and outputs are checked during the execution ....

B. Ford, G. Back, G. Benson, J. Lepreau, A. Lin, and O. Shivers. The Flux OSKit: A Substrate for OS and Language Research. In Proc. of the 16th ACM Symposium on Operating Systems Principles, Oct. 1997.

....that the kernel and server overheads, in particular context switches overheads, are minimized. Second, we have seen marked improvements in memory management approaches that enable zero copy protocols (e.g. fbufs [5] and emulated copy [3] Other advances include, improved kernel modularity [7], component model services [8] multiserver security protocols, etc. Note that we are not the only researchers who believe it is time to re examine multiservers, as a multiserver system is also being constructed on the Pebble kernel [11] In addition, there is a greater need for multiserver ....

B. Ford et al. The Flux OSKit: A substrate for OS and language research. In SOSP'97. ACM, October 1997.

....which serve data, and extensions, which adapt the behavior of the server itself by exploiting its underlying module system. All these features are available on the wide variety of platforms that run MrEd (both traditional operating systems and experimental kernels such as the OS Kit [12]) The result is a well performing Web server that accommodates natural and exible programming paradigms without burdening programmers with platform speci c facilities or complex, error prone dynamic protocols. We have deployed this server for our book s widely accessed web site. Two major areas ....

Ford, B., G. Back, G. Benson, J. Lepreau, A. Lin and O. Shivers. The Flux OSKit: A Substrate for OS and Language Research. In 16th ACM Symposium on Operating Systems Principles, October 1997. Saint-Malo, France.

No context found.

B. Ford, G. Back, G. Benson, J. Lepreau, A. Lin, and O. Shivers. The Flux OSKit: A Substrate for OS and Language Research. In Proceedings of the 16th ACM Symposium on Operating Systems Principles, pages 38--51, Oct. 1997.

No context found.

Bryan Ford, Godmar Back, Greg Benson, Jay Lepreau, Albert Lin, and Olin Shivers. The Flux OSKit: A substrate for OS and language research. In Proceedings of the 16th ACM Symposium on Operating Systems Principles, pages 38--51, St. Malo, France, October 1997.

No context found.

B. Ford, G. Back, G. Benson, J. Lepreau, A. Lin, and O. Shivers. The Flux OSKit: A substrate for OS and language research. In Proceedings of the 16th ACM Symposium on Operating Systems Principles, pages 38--51, St. Malo, France, Oct. 1997.

No context found.

B. Ford, G. Back, G. Benson, J. Lepreau, A. Lin, and O. Shivers, "The Flux OSKit: A substrate for OS and language research," in Proc. of the 16th ACM Symposium on Operating Systems Principles (SOSP '97), St. Malo, France, Oct. 1997, pp. 38--51.

....active applications on top of the Bees execution environment which runs on top of the resource controlling JVM, called JanosVM. Together, Bees and JanosVM form the EE layer of an active node and run on top of Moab, the NodeOS in Janos. Moab is an active node operating system based on the OSKit [19] that implements the active networks community standard NodeOS API specification [18] Bees based active applications on Janos forward packets at least four times slower than the fast path forwarding in Moab [12] Clearly, Bees environment is not suited for active extensions that want to add ....

B. Ford, G. Back, G. Benson, J. Lepreau, A. Lin, and O. Shivers, "The Flux OSKit: A Substrate for OS and Language Research," in Proceedings of the 16th ACM Symposium on Operating Systems Principles, Oct. 1997, pp. 38--51.

....level kernel might be a fast disk image loader, a memory file system based operating system, or typically, a larger second level bootstrap program. This second level loader again contacts the database to determine the next step, either booting from an on disk partition or downloading an OSKit [12] kernel. This multi phase approach permits flexible configuration and customization of the OS that runs on each node. The system then waits for the nodes to come back up. If a node does not come up in a timely manner, one more attempt is made; if it still fails, the entire experiment swap in ....

B. Ford, G. Back, G. Benson, J. Lepreau, A. Lin, and O. Shivers. The Flux OSKit: A Substrate for OS and Language Research. In Proc. 16th SOSP, pages 38--51, Oct. 1997.

....API such as POSIX, the emphasis of an active router on forwarding packets makes this interface unique in many ways. The second contribution is to report our experiences implementing the interface in three different OS environments: within the Scout kernel [21] using the OSKit component base [9], and above the exokernel [13] Although none of these implementations is complete, each exposes an interesting set of implementation issues for a significant subset of the NodeOS interface. II. DESIGN RATIONALE The goal of active networks is to make the network as programmable as possible, ....

....platform for other Java based EEs. Together, ANTSR and the JanosVM form the EE layer of the active network architecture. Underneath the JanosVM is Moab, a multi threaded, fully preemptible single address space operating system implementing the NodeOS abstractions. Moab is built us ing the OSKit [9], a toolkit of components for building sys tems software. The OSKit includes suites of device drivers, numerous filesystems, a networking stack, and a thread implementation, as well as a host of support code for booting, remote debugging, memory management, and enabling hosted execution on UNIX ....

Bryan Ford, Godmar Back, Greg Benson, Jay Lepreau, Albert Lin, and Olin Shivers. The Flux OSKit: A substrate for OS and language research. In Proceedings of the 16th ACM Syrup. on Operating Systems Principles, pages 38-51, St. Malo, France, October 1997.

.... language paradigms that support the unit component model: imperative languages, exemplified by C [21] functional languages, exemplified by Scheme [11] and object oriented languages, exemplified by Java [17] Sections 2 and 3) We demonstrate our approach with two examples from the OSKit [12], a set of operating system components written in C (Sections 3.2 and 3.3) We evaluate the approach by applying it to each pattern described by Gamma et al. 13] Section 3.4) and by analyzing its costs and benefits (Section 4) In summary, although the benefits of separating system ....

....participants. The system designer may want to make additional changes, such as aggregating groups of interfaces into single interfaces, to reduce the complexity of the unit descriptions. 3.2 Example: Managing Block Devices We illustrate our approach in the context of a concrete system. The OSKit [12] is a collection of components for building operating systems and standalone systems. The components are almost all written in C, with a few in assembly code. Although the OSKit includes a number of small and modest sized from scratch components, such as memory and thread management, the ....

B. Ford, G. Back, G. Benson, J. Lepreau, A. Lin, and O. Shivers. The Flux OSKit: A substrate for OS and language research. In Proc. of the 16th ACM Symposium on Operating Systems Principles, pages 38--51, St. Malo, France, Oct. 1997.

....memory controls have been implemented and tested. Extensions to the virtual machine and the Java objects to support CPU inheritance scheduling are under active development. The resulting Java based OS will run atop normal OSs in user mode, and also in kernel mode, when linked with our OSKit [5]. The latter system should provide a true Javabased OS appropriate for supporting distributed Java components. Finally, we will learn to what extent a particular OS structure can be built on drastically different protection mechanisms: initial results are promising. ....

B. Ford, G. Back, G. Benson, J. Lepreau, A. Lin, and O. Shivers. The Flux OSKit: A Substrate for OS and Language Research. In Proc. of the 17th ACM Symp. on Operating Systems Principles, pages 38--51, St. Malo, France, Oct. 1997.

....therefore seek a framework that integrates these two facets of systems modularity. We expect the Knit approach to help deal with many different aspects of systems code, including concurrency, isolation, and real time performance. We are currently exploring these aspects in the context of the OSKit [7], a large collection of components for building low level systems. Concurrency. In the OSKit, many components are single threaded because they were extracted from single threaded kernels such as Linux and BSD. However, as OSKit components, they are often used in multithreaded environments. When ....

B. Ford, G. Back, G. Benson, J. Lepreau, A. Lin, and O. Shivers. The Flux OSKit: A substrate for OS and language research. In Proc. of the 16th ACM Symposium on Operating Systems Principles, pages 38--51, St. Malo, France, Oct. 1997.

....API such as POSIX, the emphasis of an active router on forwarding packets makes this interface unique in many ways. The second contribution is to report our experiences implementing the interface in three di erent OS environments: within the Scout kernel [21] using the OSKit component base [9], and above the exokernel [13] Although none of these implementations is complete, each exposes an interesting set of implementation issues for a signi cant subset of the NodeOS interface. II. Design Rationale The goal of active networks is to make the network as programmable as possible, while ....

....platform for other Java based EEs. Together, ANTSR and the JanosVM form the EE layer of the active network architecture. Underneath the JanosVM is Moab, a multi threaded, fully preemptible single address space operating system implementing the NodeOS abstractions. Moab is built using the OSKit [9], a toolkit of components for building systems software. The OSKit includes suites of device drivers, numerous lesystems, a networking stack, and a thread implementation, as well as a host of support code for booting, remote debugging, memory management, and enabling hosted execution on UNIX ....

Bryan Ford, Godmar Back, Greg Benson, Jay Lepreau, Albert Lin, and Olin Shivers. The Flux OSKit: A substrate for OS and language research. In Proceedings of the 16th ACM Symp. on Operating Systems Principles, pages 38-51, St. Malo, France, October 1997.

No context found.

B. Ford, G. Back, G. Benson, J. Lepreau, A. Lin, and O. Shivers. The Flux OSKit: A substrate for OS and language research. In 16th ACM Symposium on Operating System Principles, October 1997.

No context found.

B. Ford, G. Back, G. Benson, J. Lepreau, A. Lin and O. Shivers, "The Flux OSKit: A substrate for OS and language research", presented at In Proceedings of the 16th ACM Symposium on Operating Systems Principles, St Malo, France, 1997.

No context found.

B. Ford, G. Back, G. Benson, J. Lepreau, A. Lin, and O. Shivers. The Flux OSKit: A substrate for OS and language research. In Proceedings of the 16th ACM Symposium on Operating Systems Principles, pages 38--51, St. Malo, France, October 1997.

No context found.

B. Ford, G. Back, G. Benson, J. Lepreau, A. Lin, O. Shivers, "The Flux OSKit: A Substrate for OS and Language Research", Proceedings of the 16th ACM Symposium on Operating Systems Principles, ACM Press, October 1997.

No context found.

B. Ford, G. Back, G. Benson, J. Lepreau, A. Lin, O. Shivers, "The Flux OSKit: A Substrate for OS and Language Research", Proceedings of the 16th ACM Symposium on Operating Systems Principles, ACM Press, October 1997.

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