| W. S. Frantz and C. R. Landau. Object-oriented transaction processing in the KeyKOS microkernel. In Proceedings of the Usenix Symposium on Microkernels and Other Kernel Architectures, pages 13--26, San Diego, California, Sept. 1993. |
....Numerous persistent object systems run at the operating system level. The operating system can use the page access patterns of running codelets to determine which pages of memory need to be made persistent. This is the approach taken by such persistent systems as Grasshopper [28] KeyKOS [39], and others. Similar approaches are taken by software distributed shared memory systems [65] to propagate changes. Finally, Howell [47] describes an implementation of Java persistence which operates above the operating system but below the language run time system. A more complete discussion of ....
W. S. Frantz and C. R. Landau. Object-oriented transaction processing in the KeyKOS microkernel. In Proceedings of the Usenix Symposium on Microkernels and Other Kernel Architectures, pages 13--26, San Diego, California, Sept. 1993.
....Numerous persistent object systems operate at the operating system level. The operating system can use the page access patterns of running codelets to determine which pages of memory need to be made persistent. This is the approach taken by such persistent systems as Grasshopper [12] KeyKOS [15], and others. Similar approaches are taken by software distributed shared memory systems [30] to propagate changes. Finally, Howell [19] describes an implementation of Java persistence which operates above the operating system but below the language runtime. A more complete discussion of operating ....
W. S. Frantz and C. R. Landau. Object-oriented transaction processing in the KeyKOS microkernel. In Proceedings of the Usenix Symposium on Microkernels and Other Kernel Architectures, pages 13--26, San Diego, California, Sept. 1993.
....solves some of the administrative problems by establishing an economic model resources are retained as long as you keep paying the rent. The Clouds operating system [56] provided persistent objects and persistent threads on a distributed network of standard computers. Similarly, the KeyKos [84] and Eros [190] operating systems offer transparent persistence for objects. Grasshopper [71] is a general purpose persistent platform. The challenge of getting applications built on an unfamiliar operating system, inhibited the use of persistent operating systems as vehicle with which to test the ....
W.S. Frantz and C.R. Landau. Object-oriented transaction processing in the KeyKOS microkernel. In USENIX Association, editor, Proceedings of the USENIX Symposium on Microkernels and Other Kernel Architectures: September 20--21, 1993, San Diego, California, USA, pages 13--26, Berkeley, CA, USA, September 1993. USENIX.
....of primitive resource types and a small set of precisely specified actions that can be performed on each resource. It is intended for currently being used as a substrate for active networking research. EROS s predecessor, KeyKOS, has been used to support production VISA transaction workloads [Har85, Lan93]. EROS provides an efficient capability implementation [Sha96c] whose performance comes within a few cycles of the limits of the underlying hardware. The system includes a generic utility for building confined subsystems: constructors 2 For purposes of verification, the essential EROS resource ....
William S. Frantz and Charles R. Landau, "Object Oriented Transaction Processing in the KeyKOS Microkernel ", Proceedings of the USENIX Workshop on Micro-Kernels and Other Kernel Architectures, USENIX Association, September 1993.
....While EROS is not yet running applications, previous implementations of the architecture have been deployed with full application environments. An evaluation of the performance of KeyTXF, the KeyKOS transaction manager for the System 370 implementation, is described by Frantz and Landau [16]. Performance on the TP1 benchmark ranged from 2.57 to 25.7 times faster than other protected database systems, and scaled linearly with CPU speed if the I O system was also upgraded for increased capacity. IBM s TPF was 22 faster (22 transactions per second vs. 18 for KeyTXF) but 181 TPF was ....
.... level benchmarks. The construction of a native EROS execution environment is expected to take several people another year, after which it will be possible to perform such measurements. The conclusion at this stage is that building such an environment is worth pursuing. Experience with KeyKOS [5, 16] suggests that the microbenchmark results reported here approximately predict real system performance. The design presented here incorporates both user level fault handling, which is not uncommon in modern microkernels, and, uniquely as far as we know, user level storage allocation. Performance ....
W. S. Frantz and C. R. Landau. Object oriented transaction processing in the KeyKOS microkernel. In Proc. USENIX Workshop on Micro-Kernels and Other Kernel Architectures, pages 13--26. USENIX Association, Sept. 1993.
....Perhaps more important, the Metagap e family is known to include two members that deliver respectable performance. The KeyKOS system runs on the S 370 and MC88000 families [Har85, Bom92] It has been used to process VISA transactions, and exhibits unusual stability in this class of applications [Lan93]. EROS, a research system at the University of Pennsylvania, has shown that the performance of capability systems can match that of access list based architectures [Sha97a, Sha96c] 2 Naming and Access Rights Metagap e describes a family of capability systems. A capability is Access Rights ....
William S. Frantz and Charles R. Landau, "Object Oriented Transaction Processing in the KeyKOS Microkernel", Proceedings of the USENIX Workshop on Micro-Kernels and Other Kernel Architectures, USENIX Association, September 1993.
....ffl primitive and limited access to individual I O devices. A number of application level operating systems have been built using these primitives, including implementations of EDX, RPS, VM 370, MVS and Unix. A transaction processing system called KeyTXF has also been implemented on KeyKOS [41]. This system yields very high transaction processing rates. The performance of the Unix implementation was comparable to that of the Mach 2.5 based Unix kernel, with some operations being slower and others considerably faster [14] Evaluation Through checkpointing KeyKOS provides fault tolerance, ....
William S. Frantz and Charles R. Landau. Object Oriented Transaction Processing in the KeyKOS Microkernel. In Proceedings of the USENIX Symposium on Microkernels and Other Kernel Architectures, pages 13--26, September 1993.
....of primitive resource types and a small set of precisely specified actions that can be performed on each resource. It is intended for currently being used as a substrate for active networking research. EROS s predecessor, KeyKOS, has been used to support production VISA transaction workloads [Har85, Lan93]. EROS provides an efficient capability implementation [Sha96c] whose performance comes within a few cycles of the limits of the underlying hardware. The system includes a generic utility for building confined subsystems: constructors For purposes of verification, the essential EROS resource ....
William S. Frantz and Charles R. Landau, "Object Oriented Transaction Processing in the KeyKOS Microkernel", Proceedings of the USENIX Workshop on Micro-Kernels and Other Kernel Architectures, USENIX Association, September 1993.
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