L. Peterson, N. Hutchinson, S. O'Malley, and M. Abott. Rpc in the x-Kernel: evaluating new design techniques. ACM Symposium on Operating Systems Principles, 1989, 91-101.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....algorithm (with a short time out value) for the consensus and reliable multicast protocols. Although applied in a di#erent context, this approach is similar to the one followed in the design of the CONDUIT framework of network protocols [28] and the x Kernel library of communication protocols [41]. 5 Asynchronous protocols vs. synchronous invocations Our Bast framework enabled us to experiment with various group protocols and algorithms. The main limitation of Bast however is its restriction to single language object groups, namely Smalltalk. We decided to reuse the experience gained ....

L. Peterson, N. Hutchinson, S. O'Malley, and M. Abott. Rpc in the x-Kernel: evaluating new design techniques. ACM Symposium on Operating Systems Principles, 1989, 91-101.

....con icting forces of synchronous G RMC and message ordering and o er a possible solution to prevent deadlocks while still preserving ordering properties. 2 JavaGroups Protocol Stack Architecture JavaGroups is a group communication toolkit based on a layered protocol stack architecture similar to [Rit84, PHOA89, VRBM96, Hay98]. An application uses a channel as group endpoint. A channel has a local address and a group address which is the name of the group. All channels with the same group address form a group. Some of the methods a channel o ers are connecting to disconnecting from a group (i.e. joining and leaving) ....

Larry L. Peterson, Norm Hutchinson, Sean O'Malley, and Mark Abbott. RPC in the x-Kernel: Evaluating new Design Techniques. In Proceedings of the Twelfth ACM Symposium on Operating Systems Principles, pages 91-101, Litcheld Park, Arizona, November 1989.

....Instead, all of this is automatically performed by the Dispatcher class. 9 Whether a message is a request or a response is determined by a flag in the message itself. 10 4 Protocol Stack The protocol stack is JavaGroups default transport (c.f. fig 1) written entirely in Java. Similar to [PHOA89, VRB95], it uses micro protocols in its implementation. A micro protocol (from now on called layer) enforces a part of the quality of service properties guaranteed by the protocol stack as a whole. The properties desired by the user of a stack are achieved by creating a layer for each property and ....

Larry L. Peterson, Norm Hutchinson, Sean O'Malley, and Mark Abbott. RPC in the x-Kernel: Evaluating new Design Techniques. In Proceedings of the Twelfth ACM Symposium on Operating Systems Principles, pages 91--101, Litchfield Park, Arizona, November 1989.

....who wish to extend BAST for new protocols, or simply to extend existing protocols within BAST will use the DTM pattern. It is a framework with a simple architecture, yet it allows the construction of fault tolerant software. Like ACE, BAST also derives concepts from STREAMS [44] x kernel [40], and Conduit [51] Conduit , in particular, is very similar to BAST, INRIA Object Oriented Frameworks for Distributed Software 15 but it decomposes the problem to a finer grain than BAST [19] and Conduit is largely a black box framework, while BAST is a gray box framework. 4.3 Higher Levels of ....

L. Peterson, N. Hutchinson, S. O'Malley, and M. Abott. Rpc in the x-kernel: Evaluating new design techniques. In Proceedings of the ACM Symposium on Operating Systems Principles, pages 91--101. ACM, nov 1989.

.... the RPC cost Chapter 5: Streams 103 103 analysis in [SB89] can be found in [CJRS89] Work on performance optimization of TCP includes [Jac88, Jac90, Kay94, KP93] A summary of other relevant papers can be found in [Com91, Ten90, BD95] Other papers included in the biliography of this text include [BMP94, Com91, CS93, CT87, DP93, EBBV95, FJML95, Jac88, Jac90, KC93, KP94, MRTR90, PHMA89, RAAB88a, RAAB88b, RST88, RST89, SDW92, Tan88, CDK94]. Kenneth P. Birman Building Secure and Reliable Network Applications 104 104 6. CORBA and Object Oriented Environments With the emergence of object oriented programming languages, such as Modula and C , came a recognition that object orientation could play a role similar to that of the OSI ....

....to achieve high performance. Both pieces of work were done out of the context of any particular operating system, but are potentially applicable to most standard vendor supported operating systems. Kenneth P. Birman Building Secure and Reliable Network Applications 150 150 The x Kernel [PHMA89] is an operating system dedicated to the implementation of network protocols for experimental research on performance, flow control, or other issues. The assumption that x Kernel applications are purely communication oriented greatly simplified the operating system design, which confines itself to ....

[Article contains additional citation context not shown here]

Larry Peterson, Norm Hutchinson, Sean O'Malley, and Mark Abbott. RPC in the x-Kernel: Evaluating New Design Techniques. In Proceedings of the 12th Symposium on Operating Systems Principles, ACM, Nov. 1989 (Litchfield Park, AZ), 91101.

....the ON, so that each layer extends or strengthens the properties of the stack of layers and ON below it. This is a way of building distributed protocols that has become popular over the past decade: it was introduced as the streams architecture of the Unix system then generalized by the x Kernel [Peterson 1989], and adapted to group structured applications in our work on the Horus [Van Renesse 1996] and Ensemble [Hayden 1998] systems. Recent work has shown how to use formal methods to reason about, optimize, and prove properties of systems structured in this manner [Liu 1999] Birman 2000] security ....

Larry Peterson, Norm Hutchinson, Sean O'Malley and Mark Abbott. RPC in the x-Kernel: Evaluating New Design Techniques. Proc. 12 th SOSP (Litchfield Park, Az), Nov. 1989, 91-101.

....designers of communication protocols and systems. The best known framework for composing a set of protocols is the STREAMS framework [17] This work does not support group communication and has limited opportunities for concurrency. A related but more sophisticated approach is used in the x kernel [13]. Horus was motivated by ideas from x kernel, but with group communication as the fundamental abstraction. x kernel is designed mainly for point to point communication, and configuration is done at compile time. Horus improves on this work by providing run time configuration, group communication ....

Larry L. Peterson, Norm Hutchinson, Sean O'Malley, and Mark Abbott. RPC in the x-Kernel: Evaluating new design techniques. In Proc. of the Twelfth ACM Symp. on Operating Systems Principles, pages 91--101, Litchfield Park, AZ, November 1989.

....typically do not access) have an efficient implementation, while the protocol headers (which protocol layers manipulate a great deal) benefit greatly from ML. Our approach with header formats takes a somewhat non standard view of how to format messages. In contrast with many other systems[PHOA93, Pos81] the formats of headers for individual layers are not defined at the byte level. In addition, the headers of a stack of protocol layers is not the concatenation of the headers of the individual layers. Instead, the system is free to format protocol headers any way so long as all endpoints ....

....systems, such as Horus, view headers as extensions to the low level representation of messages. In such systems, messages can be viewed as a stack of bytes and the application and protocols use operations to push and pop bytes onto and off of messages. This design originated with the X Kernel[PHOA93] although UNIX STREAMS has a similar feature. There are a variety of reasons for this approach, such as the need to adhere to strict, standardized header formats and the expectation that low level operations are needed to achieve high performance. Unfortunately, such designs have costs. These ....

Larry L. Peterson, Norm Hutchinson, Sean O'Malley, and Mark Abbott. RPC in the x-Kernel: Evaluating new design techniques. In Proc. of the Fourteenth ACM Symp. on Operating Systems Principles, pages 91--101, Asheville, NC, December 1993.

....subsystem, or both. Compared to its parent system Isis, Horus is smaller, provides more flexibility, and performs better. It also offers security features, and is able to deal with network partitioning. The system design integrates ideas developed in Isis, Transis [2] and the x kernel [9]. This paper discusses the architecture and implementation of Horus, reviews the interfaces supported (notably, an interface in which the cost of the protocols supporting a communication group can be varied depending on the properties desired by the user) and presents performance figures for a ....

Larry L. Peterson, Norm Hutchinson, Sean O'Malley, and Mark Abbott. RPC in the x-Kernel: Evaluating new design techniques. In Proceedings of the Twelfth ACM Symposium on Operating Systems Principles, pages 91--101, Litchfield Park, Arizona, November 1989.

....algorithm (with a short time out value) for the consensus and reliable multicast protocols. Although applied in a different context, this approach is similar to the one followed in the design of the CONDUIT framework of network protocols [26] and the x Kernel library of communication protocols [39]. 4 Asynchronous protocols vs. synchronous invocations Our Bast framework enabled us to experiment with various group protocols and algorithms. The main limitation of Bast however is its restriction to single language object groups, namely Smalltalk. We decided to reuse the experience gained ....

L. Peterson, N. Hutchinson, S. O'Malley, and M. Abott. Rpc in the x-Kernel: evaluating new design techniques. ACM Symposium on Operating Systems Principles, 1989, 91-101.

....memory reads. The VCM Approach to High Performance Cluster Computing. The reduction of software communication overheads is the principal topic addressed by our work. The method with which we approach this topic is influenced by current research on configurable operating and communication systems [3, 13, 24, 30] which has demonstrated the fact that a single set of system primitives cannot easily satisfy the requirements of every user provided application program. These insights have led to our development of a programmable communication interface, which may be tailored by applications to meet their ....

L. Peterson, N. Hutchinson, S. O'Malley, and M. Abbot, RPC in the x-Kernel: Evaluating New Design Techniques, in Proceedings of the 12th ACM Symposium on Operating Systems Principles, Association for Computing Machinery, New York, NY, 1989, pp. 91--101.

....the protocols are lined up linearly, and two reliable, sequenced channels are placed between each pair of consecutive protocols. STREAMS, however, does not support group communication and has limited opportunities for concurrency. A related but more sophisticated approach is used in the x kernel [3]. In this system, protocol objects can be linked together in acyclic graphs. Horus was motivated by ideas from x kernel, but with group communication as the fundamental abstraction. x kernel was mainly designed for point to point communication, and even simple request response style communication ....

Larry L. Peterson, Norm Hutchinson, Sean O'Malley, and Mark Abbott. RPC in the x-Kernel: Evaluating new design techniques. In Proceedings of the Twelfth ACM Symposium on Operating Systems Principles, pages 91--101, Litchfield Park, Arizona, November 1989.

....communication system that can run either in user space or in a microkernel, and that offers great flexibility in terms of the programming model exported to application developers, the properties provided by a protocol stack, and the overall system configuration. Strongly motivated by the x kernel [4], Horus system uses an architecture in which protocols are constructed by stacking small microprotocols, which support a common interface. Unlike x kernel, however, our orientation is on group communication (x kernel focuses on RPC and streams) and it was our goal to support the virtual synchrony ....

Larry L. Peterson, Norm Hutchinson, Sean O'Malley, and Mark Abbott. RPC in the x-Kernel: Evaluating new design techniques. In Proceedings of the Twelfth ACM Symposium on Operating Systems Principles, pages 91--101, Litchfield Park, Arizona, November 1989.

....is available at no fee for research use; see the Horus project page at http: www.cs.cornell.edu Info Projects HORUS for details. It does this using a structured framework for protocol composition, which incorporates ideas from systems such as the Unix streams framework [16] and the x kernel [12], but replaces point to point communication with group communication as the fundamental abstraction. In Horus, group communication support is provided by stacking protocol modules that have a regular architecture, and in which each module has a separate responsibility. A process group can be ....

....functionality such as data encryption, packing small messages for efficient communication, isochronous communication (useful in multimedia systems) etc. For Horus layers to fit like Lego blocks, they each must provide the same downcall and upcall interfaces. A lesson learned from the x kernel [12] is that if the interface is not rich enough, extensive use will be made of general purpose control operations (similar to ioctl) which reduces configuration flexibility. Since the control operations are unique to a layer, the Lego blocks would not fit as easily. The Horus Common Protocol ....

Larry L. Peterson, Norm Hutchinson, Sean O'Malley, and Mark Abbott. RPC in the x-Kernel: Evaluating new design techniques. In Proc. of the Twelfth ACM Symp. on Operating Systems Principles, pages 91--101, Litchfield Park, AZ, November 1989.

....Many low level optimizations associated with control transfer in operating systems can be recast in terms of continuations. For example, handoff scheduling [Black 90b, Thacker et al. 88] stackless kernel threads [Thacker et al. 88] asynchronous I O [Levy Eckhouse 89] kernel to user upcalls [Hutchinson et al. 89, Anderson et al. 91, Scott et al. 89] and Lightweight Remote Procedure Call [Bershad et al. 90] each represent an optimization to IPC and thread management systems that can be described and implemented in terms of continuations. Furthermore, by defining a machine independent interface to ....

....RPC request. With the ability to return out of the kernel to a context other than the one that was active at the time the kernel was entered, continuations can be used to implement a rich collection of control transfer mechanisms in a general way. For example, the upcalls required by the x kernel [Hutchinson et al. 89] and Scheduler Activations [Anderson et al. 91] can be implemented by keeping a pool of blocked threads in the kernel, each with a default return to user level continuation. To perform an upcall, the default continuation is replaced with one that transfers control out of the kernel to a ....

Hutchinson, N. C., Peterson, L. L., Abbott, M. B., and O'Malley, S. RPC in the x-Kernel: Evaluating New Design Techniques. In Proceedings of the 12th ACM Symposium on Operating Systems Principles, pages 91--101, December 1989.

....protocols. One of these channels is for transporting user data, while the other channel carries protocol control messages. STREAMS, however, does not support group communication and has limited opportunities for concurrency. A related but more sophisticated approach is used in the x kernel [11]. In this system, protocol objects can be linked together in acyclic graphs. Horus was motivated by ideas from x kernel, but with group communication as the fundamental abstraction. x kernel was mainly designed for point to point communication, and even simple request response style communication ....

Larry L. Peterson, Norm Hutchinson, Sean O'Malley, and Mark Abbott. RPC in the x-Kernel: Evaluating new design techniques. In Proc. of the Twelfth ACM Symp. on Operating Systems Principles, pages 91--101, Litchfield Park, AZ, November 1989.

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