TY - GEN
T1 - EROS
T2 - 17th ACM Symposium on Operating Systems Principles, SOSP 1999
AU - Shapiro, Jonathan S.
AU - Smith, Jonathan M.
AU - Farber, David J.
N1 - Funding Information:
However, the desirable features of transparent persistence and capability-based protection are widely believed to have prohibitive performance. This belief is largely justified by experience. The performance issues of the i432 have been examined by C01well \[7\],a nd those of Mach by Ford \[14\]. While the IBM AS/400 \[47\]( a.k.a. System 38) has been a large-scale commercial success, its performance depends on * This research was supported by DARPA under Contracts #N66001-96-C-852, #MDA972-95-1-0013, and #DABT63-95-C-0073. Additional sup-port was provided by the AT&T Foundation, and the Hewlett-Packard, TandemC omputerand lntel Corporations. t Author now with the IBM T. J. Watson Research Center.
Publisher Copyright:
© 1999 ACM.
PY - 1999/12/12
Y1 - 1999/12/12
N2 - EROS is a capability-based operating system for commodity processors which uses a single level storage model. The single level store's persistence is transparent to applications. The performance consequences of support for transparent persistence and capability-based architectures are generally believed to be negative. Surprisingly, the basic operations of EROS (such as IPC) are generally comparable in cost to similar operations in conventional systems. This is demonstrated with a set of microbenchmark measurements of semantically similar operations in Linux. The EROS system achieves its performance by coupling well-chosen abstract objects with caching techniques for those objects. The objects (processes, nodes, and pages) are well-supported by conventional hardware, reducing the overhead of capabilities. Software-managed caching techniques for these objects reduce the cost of persistence. The resulting performance suggests that composing protected subsystems may be less costly than commonly believed.
AB - EROS is a capability-based operating system for commodity processors which uses a single level storage model. The single level store's persistence is transparent to applications. The performance consequences of support for transparent persistence and capability-based architectures are generally believed to be negative. Surprisingly, the basic operations of EROS (such as IPC) are generally comparable in cost to similar operations in conventional systems. This is demonstrated with a set of microbenchmark measurements of semantically similar operations in Linux. The EROS system achieves its performance by coupling well-chosen abstract objects with caching techniques for those objects. The objects (processes, nodes, and pages) are well-supported by conventional hardware, reducing the overhead of capabilities. Software-managed caching techniques for these objects reduce the cost of persistence. The resulting performance suggests that composing protected subsystems may be less costly than commonly believed.
UR - http://www.scopus.com/inward/record.url?scp=85007616439&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=85007616439&partnerID=8YFLogxK
U2 - 10.1145/319151.319163
DO - 10.1145/319151.319163
M3 - Conference contribution
AN - SCOPUS:85007616439
T3 - Proceedings of the 17th ACM Symposium on Operating Systems Principles, SOSP 1999
SP - 170
EP - 185
BT - Proceedings of the 17th ACM Symposium on Operating Systems Principles, SOSP 1999
PB - Association for Computing Machinery, Inc
Y2 - 12 December 1999 through 15 December 1999
ER -