Welch, B., "The Sprite Remote Procedure Call System", UCB/CSD 86/302, University of California at Berkeley, June 1988. 7. Security Considerations Security issues are not discussed in this memo.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....on SUN 2 and SUN 3 workstations. Contact: Fred Douglis or Michael N. Nelson, Computer Science Division, University of California at Berkeley, 571 Evans Hall, Berkeley, CA 94720. For principal investigation, contact John Ousterhout at UC Berkeley. References: 308] 309] 310] 311] 312] [313], 314] 2.49 SWALLOW Main Goal SWALLOW is a distributed file system supporting highly reliable object oriented data storage. It provides all kind of transparency levels, i.e. those of location, access, concurrency, failure, and replication. Advantages SWALLOW is yet another object oriented ....

B.B. Welch, "The Sprite Remote Procedure Call System", Technical Report UCB/CSD 86/302, Computer Science Division, Univ. of California Berkeley, Berkeley, California 94720, June 1986.

....protocol. 1 INTRODUCTION Several distributed operating systems such as V system, DASH, Sprite, and Mach, have been designed and implemented. Among those operating systems, V system developed their own transport layer protocol, VMTP[Cheriton 86] and Sprite implemented their own network protocol[Welch 86] These two protocols are suitable for applications using remote procedure calls. DASH proposed a new communication abstraction, channels[Anderson 89] which provide communication paths with user desired qualities. Although new protocols for the transport layer and new concepts of communications ....

Brent B. Welch. The Sprite Remote Procedure Call System. Technical Report UCB/CSD 86/302, Computer Science Division (EECS), University of California, Berkeley, June 1986.

....transactions. Interprocess communication is a distributed operating system facility whose performance has been extensively studied, in contrast to other facilities or issues. Unfortunately, these studies have been carried out mainly for one particular system [Cheriton 1988] Rashid 1986] [Welch 1986]. This implies that it is very hard to say which form of interprocess communication offers the best performance. 3.4. Group communication 3.4.1. Basic Features Group communication is an operating system abstraction which supports the programmer by offering convenience and clarity. This ....

B. B. Welch, "The Sprite Remote Procedure Call System," Report No. UCB/ CSD 86/302, Computer Science Division (EECS), University of California, 1986.

....the x kernel to the Sprite operating system. Comparing the x kernel to Sprite is interesting because, like other recent experimental systems [7, 35] Sprite is optimized to support a particular RPC protocol. Specifically, Sprite implements an RPC protocol that supports at most once semantics [37]. We compared an implementation of Sprite RPC in the x kernel with a native implementation whose performance was also measured on a Sun 3 75. 6 Both versions were compiled using the standard Sun C compiler. The latency and throughput results are presented in Table VI. x Kernel Sprite Latency ....

B. B. Welch. The Sprite remote procedure call system. Technical Report UCB/CSD 86/302, University of California Berkeley, Berkeley, Calif., June 1988. 26

....3) ACK ACK Data Data Destination process Network Kernel Figure 3: Kernel resident protocols reduce domain crossing User level access to the data link layer is not universally regarded as a good thing. Some have suggested that user programs never need access to explicit network communication [23]; others might argue that all networking should be done within a transport protocol such as IP [19] or the ISO Transport Protocol [15] with demultiplexing done by the transport layer code. Both these arguments implicitly assume a homogeneous networking environment, but heterogeneity is often a ....

Brent B. Welch. The Sprite Remote Procedure Call System. UCB/CSD 86/302, Department of Electrical Engineering and Computer Science, University of California ---- Berkeley, June, 1986. THE PACKET FILTER ii THE PACKET FILTER

....graph that implements an RPC service. The graph, as illustrated in Figure 2, contains three protocols. The topmost protocol implements the Birrell Nelson remote procedure call algorithm [5] To make the example more concrete, we use an actual protocol that implements this algorithm Sprite RPC [37]. IP is a protocol that routes messages across the internet [27] and ETH is a device driver protocol for the ethernet. 2 IP IP Sprite Sprite RPC RPC ETH Figure 2: Stage 0 Conventional RPC 3.1 Encapsulating Algorithms as Protocols Many traditional protocols implement several different ....

B. B. Welch. The Sprite remote procedure call system. Technical Report UCB/CSD 86/302, University of California Berkeley, Berkeley, Calif., June 1988.

....Module ETH implements the device independent Ethernet protocol processing and module LANCE implements the driver for the Ethernet adapter present in the DEC 3000 machine. The right hand side of Figure 4.1 shows the RPC stack. It implements a remote procedure call facility similar to Sprite RPC [110]. As the figure shows, the RPC stack is 113 TCPTEST TCP IP VNET ETH LANCE VNET ETH XRPCTEST MSELECT VCHAN CHAN BID BLAST IP LANCE Figure 4.1: Test Protocol Stacks considerably taller than the one for TCP IP. At the top is module XRPCTEST, which is the RPC equivalent of the ping pong test ....

Brent B. Welch. The Sprite remote procedure call system. Technical Report UCB/CSD 86/302, Computer Science Division, EECS Department, University of California, Berkeley, June 1986. http://sunsite.Berkeley.EDU/NCSTRL/.

....at operating system boot time. In this case, the transport system often provides protocol support based only upon general usage assumptions such as unreliable datagram service (e.g. UDP) versus reliable byte stream service (e.g. TCP) Many well known transport systems belong to this category [12, 13, 14, 15, 16]. ffl Dynamic Transport Systems: postpone complete configuration until either connection establishment time or during data transfer. In both cases, these transport systems may be configured by negotiating with (1) local and remote hosts and (2) intermediate switching nodes in the network. This ....

B. B. Welch, "The Sprite Remote Procedure Call System," Tech. Rep. UCB/CSD 86/302, Computer Science Division (EECS), University of California, Berkeley, CA 94720, June 1986.

....as open, close, read, and write. Although Sprite appears similar in function to UNIX, we have completely reimplemented the kernel in order to provide better network integration. In particular, Sprite s implementation is based around a simple kernel to kernel remote procedurecall (RPC) facility [Wel86], which allows kernels on different workstations to request services of each other using a protocol similar to the one described by Birrell and Nelson [BiN84] The Sprite file system uses the RPC mechanism extensively for cache management. 1.3. Thesis Overview This dissertation covers three areas: ....

B. B. Welch, "The Sprite Remote Procedure Call System", Technical Report UCB/Computer Science Dpt. 86/302, University of California, Berkeley, June 1986.

....are one of the most widely used methods for distributed computation. Some remote procedure call environments have been integrated into the kernels of operating systems. Examples of these include XINU S RPC facility [41] the implementation of RPC in the Berkeley UNIX kernel [49] and Sprite RPC [48]. The Berkeley UNIX RPC and Sprite RPC facilities were largely experimental. Implementing RPC facilities in the kernel makes remote procedure calls significantly faster. However, this makes it impossible to expand them to heterogeneous environments. Since our intent was to create a convenient ....

B. B. Welch. The Sprite remote procedure call system. Technical Report UCB/CSD 86/302, University of California at Berkeley, June 1986.

....scales. This section describes how data are transferred between the clients and the servers in the prototype, allowing data transfer to be both efficient and scalable. 5.3. 1 Remote Procedure Calls The clients and servers in the Zebra prototype communicate via Sprite remote procedure calls (RPC) Welch86] A remote procedure call emulates a procedure call over the network. The client sends parameters to the server, and the server sends a reply. Sending an RPC is a synchronous operation, so that the process that initiates an RPC does not continue processing until the reply to the RPC has been ....

Brent B. Welch, "The Sprite Remote Procedure Call System", Technical Report UCB/CSD 86/302, Computer Science Division, University of California, Berkeley, June 1986.

....such as open, close, read, and write. Although Sprite appears similar in function to UNIX, we have completely reimplemented the kernel in order to provide better network integration. In particular, Sprite s implementation is based on a simple kernel to kernel remote procedure call (RPC) facility [17], which allows kernels on different workstations to request services of each other using a protocol similar to the one described by Birrell and Nelson [2] The Sprite file system uses the RPC mechanism extensively for cache management. 3. BACKGROUND WORK The main motivation for the Sprite cache ....

WELCH, B. The Sprite remote procedure call system. Tech. Rep. UCB/CSD 86/302, Computer Science Div. (EECS), Univ. of California, Berkeley, Calif., 1986.

No context found.

Welch86b. B. B. Welch, "The Sprite Remote Procedure Call System", Technical Report UCB/Computer Science Dpt. 86/302, University of California, Berkeley, June 1986.

No context found.

Welch86a. B. B. Welch, "The Sprite Remote Procedure Call System", Technical Report UCB/Computer Science Dpt. 86/302, University of California, Berkeley, June 1986.

No context found.

Welch, B. The Sprite Remote Procedure Call System. Technical report UCB/CSD 86/302, June 1986.

No context found.

Welch86a. B. B. Welch, "The Sprite Remote Procedure Call System", Technical Report UCB/Computer Science Dpt. 86/302, University of California, Berkeley, June 1986.

No context found.

Welch86a. B. B. Welch, The Sprite Remote Procedure Call System, Technical Report UCB/Computer Science Dpt. 86/302, University of California, Berkeley, June 1986.

....as open, close, read, and write. Although Sprite appears similar in function to UNIX, we have completely reimplemented the kernel in order to provide better network integration. In particular, Sprite s implementation is based around a simple kernel to kernel remote procedure call (RPC) facility [WELCH86b], which allows kernels on different workstations to request services of each other using a protocol similar to the one described by Birrell and Nelson [BIRR84] The Sprite file system uses the RPC mechanism extensively for cache management. 3. Background Work The main motivation for the Sprite ....

Welch, B. "The Sprite Remote Procedure Call System." Technical Report UCB/CSD 86/302, Computer Science Division (EECS), University of California, Berkeley, 1986.

No context found.

Welch, B., "The Sprite Remote Procedure Call System", UCB/CSD 86/302, University of California at Berkeley, June 1988. 7. Security Considerations Security issues are not discussed in this memo.

No context found.

Welch, B.B. The Sprite Remote Procedure Call System. Technical Report, The University of California, Berkeley, CA, No. UCB/CSD 86/302, June 1986.

No context found.

B. B. Welch. The Sprite remote procedure call system. Technical Report UCB/CSD 86/302, University of California Berkeley, Berkeley, Calif., June 1988.

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