Take a look at the new version of this page: [ beta version ]. Tell us what you think.

ABSTRACT

Lightweight Remote Procedure Call (LRPC) is a communication facility designed and optimized for communication between protection domains on the same machine. In contemporary small-kernel operating systems, existing RPC systems incur an unnecessarily high cost when used for the type of communication that predominates — between protection domains on the same machine. This cost leads system designers to coalesce weakly-related subsystems into the same protection domain, trading safety for performance. By reducing the overhead of same-machine communication, LRPC encourages both safety and performance. LRPC combines the control transfer and communication model of capability systems with the programming semantics and large-grained protection model of RPC. LRPC achieves a factor of three performance improvement over more traditional approaches based on independent threads exchanging messages, reducing the cost of same-machine communication to nearly the lower bound imposed by conventional hardware. LRPC has been integrated into the Taos operating system of the DEC SRC Firefly multiprocessor workstation.

REFERENCES

• Birrell & Nelson 84: Andrew D. Birrell , Bruce Jay Nelson, Implementing remote procedure calls, ACM Transactions on Computer Systems (TOCS), v.2 n.1, p.39-59, February 1984 [doi>10.1145/2080.357392]
• Cheriton 88: David Cheriton, The V distributed system, Communications of the ACM, v.31 n.3, p.314-333, March 1988 [doi>10.1145/42392.42400]
• Clark 85: David D. Clark, The structuring of systems using upcalls, Proceedings of the tenth ACM symposium on Operating systems principles, p.171-180, December 1985, Orcas Island, Washington, United States [doi>10.1145/323647.323645]
• Cook 78: Cook, D. The Evaluation of a Protection System. PhD dissertation, Cambridge University, Computer Laboratory, April 1978.
• Dennis & Van Horn 66: Jack B. Dennis , Earl C. Van Horn, Programming semantics for multiprogrammed computations, Communications of the ACM, v.9 n.3, p.143-155, March 1966 [doi>10.1145/365230.365252]
• Fitzgerald 86: Robert Patrick Fitzgerald, A performance evaluation of the integration of virtual memory management and inter-process communication in accent (operating system, copy-on-write), 1986
• Jones & Rashid 86: Michael B. Jones , Richard F. Rashid, Mach and Matchmaker: kernel and language support for object-oriented distributed systems, Conference proceedings on Object-oriented programming systems, languages and applications, p.67-77, September 29-October 02, 1986, Portland, Oregon, United States [doi>10.1145/28697.28705]
• Karger 89: Paul A. Karger, Using registers to optimize cross-domain call performance, Proceedings of the third international conference on Architectural support for programming languages and operating systems, p.194-204, April 03-06, 1989, Boston, Massachusetts, United States [doi>10.1145/70082.68201]
• Lampson 84: Lampson, B. W. Hints for Computer System Design. IEEE Software, 1(1):11-28, January 1984.
• Mealy et al. 66: Mealy, G., Witt, B., and Clark, W. The Functional Structure of OS/360. IBM Systems Journal, 5(1):3-51, 1966.
• Rashid 86: Richard F. Rashid, From RIG to Accent to Mach: the evolution of a network operating system, Proceedings of 1986 ACM Fall joint computer conference, p.1128-1137, November 1986, Dallas, Texas, United States
• Redell et al. 80: David D. Redell , Yogen K. Dalal , Thomas R. Horsley , Hugh C. Lauer , William C. Lynch , Paul R. McJones , Hal G. Murray , Stephen C. Purcell, Pilot: an operating system for a personal computer, Communications of the ACM, v.23 n.2, p.81-92, Feb. 1980 [doi>10.1145/358818.358822]
• Ritchie & Thompson 74: Dennis M. Ritchie , Ken Thompson, The UNIX time-sharing system, Communications of the ACM, v.17 n.7, p.365-375, July 1974 [doi>10.1145/361011.361061]
• Rovner et al. 85: Rovner, P., Levin, R., and Wick, J. On Extending Modula-2 For Building Large, Integrated Systems. Technical Report ~ 3, Digital Equipment Corporation Systems Research Center, Palo Alto, California, January 1985.
• Sandberg et al. 85: Sandberg, R., Goldberg, D., Steve Kleiman, D. W., and Lyon, B. Design and Implementation of the SUN Network Filesystem. In Proceedings o/the 1985 USENIX Summer Conference, pages 119- 130, 1985.
• Schroeder & Burrows 89: M. Schroeder , M. Burrows, Performance of Firefly RPC, Proceedings of the twelfth ACM symposium on Operating systems principles, p.83-90, November 1989 [doi>10.1145/74850.74859]
• Thacker et al. 88: Charles P. Thacker , Lawrence C. Stewart , Edwin H. Satterthwaite, Jr., Firefly: A Multiprocessor Workstation, IEEE Transactions on Computers, v.37 n.8, p.909-920, August 1988 [doi>10.1109/12.2243]
• Tzou & Anderson 88: Shin Tzou , David P. Anderson, A Performance Evaluation of the Dash Message-Passing System, University of California at Berkeley, Berkeley, CA, 1988
• van Renesse et al. 88: Robbert van Renesse , Hans van Staveren , Andrew S. Tanenbaum, Performance of the world's fastest distributed operating system, ACM SIGOPS Operating Systems Review, v.22 n.4, p.25-34, Oct. 1988 [doi>10.1145/54289.54291]
• Williamson 89: Williamson, C., January 1989. Personal communication.

INDEX TERMS

Primary Classification:
  D. Software
  D.4 OPERATING SYSTEMS
      D.4.4 Communications Management
          Subjects: Network communication

Additional Classification:
  C. Computer Systems Organization
  C.2 COMPUTER-COMMUNICATION NETWORKS
      C.2.4 Distributed Systems
          Subjects: Network operating systems

  D. Software
  D.4 OPERATING SYSTEMS
      D.4.8 Performance
          Subjects: Measurements

General Terms:
Design, Performance