Hutchinson, N. and Peterson, L. "The x-kernel: an architecture for implementing network protocols" IEEE Transactions on Software Engineering, Vol. 17, Issue 1, 1991, pp 64-76.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....protocol stacks, universal asynchronous protocol interfaces, object oriented transport components, configurable protocol stacks, and so on [6 9] all address the issue of programmable transport, but do not consider issues of QoS. Reference [10, 11] addresses both QoS and programmability issues; [12] presents the x kernel, an operating system environment that provides an explicit architecture for constructing and composing network protocols. Reference [13] also provides a taxonomy of key transport system services and illustrates the concepts with a survey of four operating system transport ....

....objects that fully implement protocol state machines with all of their functionality (e.g. TCP, XDR) In our approach, protocol stacks are dynamically, and possibly remotely, configured. In [11] the protocol state machines are dynamically (and locally) configured based on application needs. In [12] the x kernel is presented. The x kernel is an operating system with special kernel support for network protocols (e.g. memory map, buffer management, and event managers) Initially, protocol stacks are statically specified using a graph when the kernel is configured. When the kernel is booted, ....

N. C. Hutchinson and L. L. Peterson, "The x-Kernel: An Architecture for Implementing Network Protocols," IEEE Trans. Software Eng., vol. 17, no. 1, Jan. 1991, pp. 64--76.

....principle . They suggested Integrated Layer Processing (ILP) for efficiency reasons. That is, combining the operations done in different layers into one. Other systems relax layering constraints by allowing protocol implementations to be composed from protocol entities [9] 10] The x Kernel [11] works similarly, allowing an objectoriented like approach, where the relationship between protocol objects with uniform interfaces are defined to create protocol paths through the protocol objects. However, none of the above systems provide the application programmer with more flexibility. b) ....

....Different APIs: Fbufs [12] were an efficient way of passing data between levels. This included the passing between system layers and application layers. Banga et al. 13] proposed different operating system abstractions to support high performance networking aimed at servers. The x Kernel system [11] defined an abstraction aimed at improving the performance of most common patterns of interaction . As described above these systems maintain the encapsulations of the API in system software, thus restricting the application. c) Application steering of protocols: UNIX STREAMS [14] allows the ....

N. C. Hutchinson and L. L. Peterson, "The x-kernel: An architecture for implementing network protocols," IEEE Transactions on Software Engineering, vol. 17, no. 1, pp. 64--76, 1991.

....ordinary users fine grained control. Alternatively, extensions were developed for both operating systems to allow applications to define application specific handlers that may be installed directly into the kernel (Plexus [14] and ASHs [27] Operating systems such as Scout [21] and x kernel [16] were designed explicitly to support sophisticated network based applications. In these systems, users may even redefine network or transport layer protocol functions in an application specific fashion [6] With TESLA, our goal is to bring some of the power of these systems to commodity ....

HUTCHINSON, N. C., AND PETERSON, L. L. The xkernel: An architecture for implementing network protocols. IEEE Transactions on Software Engineering 17,1 (Jan. 1991), 64--76.

....problems. The design of ZEN s pluggable GIOP messaging framework is influenced by prior research on the design and optimization of protocol frameworks for communications. This section outlines this research and compares it with our work on ZEN. Configurable communication frameworks: The x kernel [14], Conduit [15] System V STREAMS [16] ADAPTIVE [17] and F CSS [18] are all configurable communication frameworks that provide a protocol backplane consisting of standard, reusable services that support network protocol development and experimentation. These frameworks support flexible ....

N. C. Hutchinson and L. L. Peterson, "The x-kernel: An Architecture for Implementing Network Protocols," IEEE Transactions on Software Engineering, vol. 17, pp. 64--76, January 1991.

....generated requests and collected results were developed. For our purposes, the network and the participating machines were overloaded to their limits, which presented additional challenges. 5. RELATED WORK Prototyping and simulation tools. The x kernel and the corresponding simulation tool x sim [23] constitute an object oriented C framework that has similarities with Neko. It is designed for building (lower level) protocol stacks. Efficient execution of the resulting protocols is a major goal. Instead, Neko s focus is easy prototyping of distributed protocols applications. Neko is a much ....

N. C. Hutchinson and L. L. Peterson, "The x-Kernel: An architecture for implementing network protocols," IEEE Transactions on Software Engineering, Vol. 17, 1991, pp. 64-76; http://www.cs.arizona.edu/xkernel/.

....of these bottlenecks, and identified mechanisms that are at least partially effective in overcoming some of the handicaps. This is evidenced by the considerable litearature that has been published in recent years on network interface design, and on the structuring of protocols in operating systems [2,5,6,7,10,12,14,28,32,39,41]. We have attempted to integrate a number of these proven good mechanisms, along with some new ones of our own creation, in our attempt to build a state of the art high performance network interface. This document describes the design and implementation of this network interface chip (NIC) ....

Hutchinson, N.C., and Peterson, L.L., "The x-Kernel: An architecture for implementing network protocols," IEEE Trans. Software Engineering, Vol. 17, No. 1, Jan. 1991.

....and network layer in a similar transputer environment. 12] also uses a multi processor transputer platform to measure the performance of several data link layer protocols. Other studies have investigated message based process architectures. All these studies utilize shared memory platforms. [13] measured the performance of the TCP, UDP, and IP protocols using a Message Parallelism process architecture on a uniprocessor platform running the x kernel. 1] measures the impact of synchronization on Message Parallelism implementations of TCP and UDP transport protocols built within a ....

....Queue subclass 3. Inserting the Module into a Stream object at the appropriate level (e.g. the transport layer, network layer, data link layer, etc. The ASX framework incorporates concepts from several other modular communication frameworks including System V STREAMS [17] the x kernel [13], and the Conduit [18] a survey of these and other communication frameworks appears in [19] These frameworks all contain features that support the flexible configuration of communication subsystems by inter connecting building block protocol components. These frameworks encourage the ....

N. C. Hutchinson and L. L. Peterson, "The x-kernel: An Architecture for Implementing Network Protocols," IEEE Transactions on Software Engineering, vol. 17, pp. 64--76, January 1991.

....crossing protection domains, incurs overhead in the form of procedure calls, context switches and duplicate work performed in different layers. The x kernel operating system combines a framework for high performance network protocol implementations with support for modular protocol composition [50]. It provides basic low level services such as thread management, buffer management and event handling that are optimized for network protocol processing. High performance is achieved by avoiding context switches and by providing a streamlined interface both between protocols 46 within the kernel ....

N.C. Hutchinson and L.L. Peterson, "The x-Kernel: An Architecture for Implementing Network Protocols," IEEE Trans. Software Engineering, vol. 17, no 1, Jan. 1991, pp. 64-76.

....ad hoc analysis functions. II. RELATED WORK Previous researchers have developed modular software architectures for extensible systems [1] 2] but few optimized for churning through large amounts of data. Other researchers have built extensible systems for streaming data through protocol layers [3] or routing functions [4] but have not provided an infrastructure that is particularly amenable to analyzing extremely large or broad datasets. Windmill [5] provides a modular system for monitoring network protocol events, but does not provide any significant infrastructure to aid in the analysis ....

N. C. Hutchinson and L. L. Peterson, "The x-Kernel: An architecture for implementing network protocols," IEEE Transactions on Software Engineering, vol. 17, no. 1, pp. 64--76, 1991.

....retained in the network due to partial failures. Given these tradeoffs, ants is based on soft state that is expired after an interval defined by the service developer. Second, there are no timer functions. Timers are often included in other protocol construction kits, for example, the x kernel [ Hutchinson and Peterson, 1991 ] because they have a straightforward application to the implementation of reliability functions. I decided not to provide them because it proved possible to emulate them without complicating the active node design; they could be added to a future version of the architecture as long as their ....

....that the existing Internet, but appear limited in their abilities to introduce new services when compared to active networks. 6.1. 1 The x kernel The x kernel provided a collection of protocol elements (called micro protocols) along with a generic mechanism for composing them based on layering [ Hutchinson and Peterson, 1991 ] It demonstrated that larger protocols, such as remote procedure call (RPC) could be expressed in terms of many smaller components with the layering model while still resulting in a high performance implementation [ O Malley and Peterson, 1992 ] While the thrust of the system was to ....

Norman C. Hutchinson and Larry L. Peterson. The xKernel: An Architecture for Implementing Network Protocols. IEEE Transactions on Software Engineering, 17(1):64--76, January 1991.

....extendable library of Ptolemy actors that implement common on chip network protocols. Designers create stack models by assembling protocol actors. Synthesis tools use knowledge of the underlying formalisms to turn the models into implementations. Previous research projects, including the x kernel [8] and the CLICK [10] modular router, also create frameworks for working with networking protocols, yet do not address the specific issues of programmable NOCs that are the focus of MESCAL. 4.2 MESCAL Communication Architecture The programmable nature of MESCAL architectures provides flexibility ....

N. C. Hutchinson and L. L. Peterson. "The x-kernel: an architecture for implementing network protocols". IEEE Transactions on Software Engineering, Vol. 17, No. 1, pp. 64-76.

....of the internal management issues of distribution. The new ISIS system has several well defined layers. The lowest layers, which implement multicast transport and failure detection, are near completion and currently run on SUN OS using SUN LWP threads, on MACH using C Threads, and on the x kernel [5]. This system can use several different network protocols at the same time, such as IP, UDP (with or without multicast support) and raw Ethernet. This enables processes on SUN OS, MACH, and Chorus to multicast among each other, even though the environments are very dissimilar. The system makes ....

N. Hutchinson and L. Peterson, "The x-Kernel: An Architecture for Implementing Network Protocols, " IEEE Transactions on Software Engineering, Vol. 17, No. 1, January 1991.

....in the field of real time and embedded systems and BeOS [Be,00] in the field of multimedia applications. In addition, a myriad of research based custom operating systems (including Serpent [Waddington,99] Roadrunner [Miller,96] Pegasus Nemesis [Mullender,94] SUMO [Coulson,93] x kernel [Hutchinson,91] Scout [Montz,94] and RT Mach [Tokuda,90] have demonstrated superior support for particular application domains compared to conventional operating systems such as Unix. Custom operating systems can be constructed in any of the three architectural forms described below, but they are of limited ....

....no need to enable the function to be dynamically extensible because the purpose of the node is necessarily static, e.g. a palmtop computer with no disk could never be used for video storage. The configurable protocol work leverages an earlier project from Arizona university, namely the x kernel [Hutchinson,91] In this system (and therefore in Scout) it is possible to configure a kernel at build time with a number of protocol units and have applications dynamically compose them to form communication sessions as required. Protocol selection is specified via textual or graphical scripting tools in terms ....

Hutchinson, N., Peterson, L., "The x-Kernel: An Architecture for implementing network protocols". IEEE Transactions on Software Engineering, 17(1), pp 64-76, 1991.

....initially developed from the NEST (Network Simulation Testbed) for comparing the fair queuing gateway algorithm with first come first served scheduling, and is used for various purposes. X Sim is a network simulator based on the x kernel, an object based network protocol implementation framework [4]. Ns is a simulation tool developed by the Network Research Group at the Lawrence Berkeley National Laboratory. It is an event driven simulation engine and intended to explore the behavior inherent to the underlying congestion control algorithms [3] Paxson reports on a large scale experiment to ....

N.C. Hutchinson and L.L. Peterson, "The x-kernel: An architecture for implementing network protocols," IEEE Transactions on Software Engineering, pp. 64--76, January 1991.

....efficiently. Da CaPo offers a set of protocol functions implemented in terms of software modules that run in an efficient run time system, the Lift algorithm. Efficient run time support for general protocol processing tasks has been investigated, e.g. in the x kernel for modular protocols [11], the Scout operating system for path based module interconnections [12] and the Crossbow project supporting a high performance toolkit for experimenting with IP (Internet Protocol) next generation protocols [13] In particular, for middleware supporting tailored communication protocols ....

L. Peterson N. Hutchinson, "The x-Kernel: An architecture for implementing network protocols," IEEE Transactions on Software Engineering, vol. 17, no. 1, pp. 64--76, Jan. 1991.

....on the desired properties and linking them together with a runtime system to give a composite protocol, which is then composed hierarchically with other composite protocols and standard protocols to form the network subsystem. When compared with similar systems for building configurable protocols [9], 10] 11] 12] Cactus provides finer granularity, a two level composition model with both hierarchical and non hierarchical composition, and a flexible and dynamic event mechanism that maximizes the configurability of micro protocols. Several prototype implementations of Cactus have been ....

....that are executed when a specified event occurs. Once constructed, a composite protocol is composed hierarchically with other protocols to form the network subsystem. In the case of the Linux version of Cactus used to implement CTP, support for hierarchical composition is provided by the x kernel [9]. The Cactus runtime system provides a variety of operations for managing events and event handlers. In particular, operations are provided for binding an event handler to a specified event and for raising an event, which causes all the handlers bound to that event to be executed. An event can ....

[Article contains additional citation context not shown here]

N. Hutchinson and L. Peterson, "The x-kernel: An architecture for implementing network protocols," IEEE Transactions on Software Engineering, vol. 17, no. 1, pp. 64--76, Jan 1991.

....via location independent send( and receive( primitives which determine the destination from the target task identity then use the communication subsystem architecture described in Chapter 4 to send messages to the recipient. Our communication protocol stack is implemented using x kernel 3. 2 [60], and is layered on top of a UDP IP stack. Based on CLIPS, the communication subsystem architecture on each host supports prioritized, bounded time message delivery which enables RTPOOL to determine the effect of communication delays on the schedulability of periodic tasks as will be described in ....

N. C. Hutchinson and L. L. Peterson, "The x-Kernel: An architecture for implementing network protocols," IEEE Transactions on Software Engineering, vol. 17, no. 1, pp. 64--76, January 1991.

....is preferred for further exploration of the performance characteristics of a protocol. 15 3.4 The x kernel protocol framework Our approach to testing the performance of the various TCP versions was a little bit different from the ones discussed above. We used the x kernel protocol framework [12], which provides implementations that are close to actual full protocol implementations. For example, the x kernel bundled TCP contains a significant part of the BSD TCP implementation. Moreover, the transfers are not simulated, i.e. real bytes are transferred over a real network. The problem we ....

....that includes one or more wireless links, under various categories of error models. At the same time we are interested in hosts that are not highend in terms of computational power, like modern handheld PCs, personal digital assistants (PDAs) and WAP phones. The use of the x kernel framework [12] enabled us to have a protocol implementation that is as close to real world implementations as possible. At the same time, this choice allowed us to achieve a high latency environment. For example, although an ordinary ping test between the two hosts takes on the average a time of less than 1 ....

N. C. Hutchinson and L. L. Peterson. "The x-kernel: An architecture for implementing network protocols". IEEE Transactions on Software Engineering, 17(1): 64-76, Jan. 1991.

No context found.

N. C. Hutchinson and L. L. Peterson, `The x-kernel: an architecture for implementing network protocols', IEEE Trans. Software Engineering, 17, 64--76 (1991).

No context found.

Hutchinson, N. and Peterson, L. "The x-kernel: an architecture for implementing network protocols" IEEE Transactions on Software Engineering, Vol. 17, Issue 1, 1991, pp 64-76.

No context found.

N. Hutchinson and L. Peterson, "The x-kernel: An Architecture for Implementing Network Protocols," IEEE Transactions on Software Engineering, vol. 17, no. 1, January 1991.

No context found.

N.C. Hutchinson and L.L. Peterson. The xkernel: an architecture for implementing network protocols. IEEE Trans. on Soft. Eng., 17(1), January 1991.

No context found.

Hutchinson, C. Norman, and, Peterson, Larry L., "The x-Kernel: An Architecture for implementing Network Protocols", IEEE Transaction on Software Engineering, Jan. 1991.

No context found.

N. Hutchinson and L. Peterson. "The x-kernel: An Architecture for Implementing Network Protocols." IEEE Transactions on Software Engineering, vol. 17, no. 1, January 1991.

No context found.

N. C. Hutchinson, L. L. Peterson; "The x-Kernel: An architecture for implementing network protocols "; IEEE Transactions on Software Engineering, 17(1):64#76, Jan. 1991.

First 50 documents  Next 50

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