M. Fiuczynski, R. Martin, T. Owa, and B. Bershad. Spine: A safe programmable and integrated network environment. In Eight ACM SIGOPS European Workshop, September 1998.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....of the large number of disks in servers to form a powerful parallel computing engine. There are network devices in this class as well. The Myrinet NIC has embedded processors that can execute user programs. Many research efforts take advantage of this computing power in different situations [5, 7, 12]. The main differences in our approach are that the intelligence lies in the switch rather than in the end devices, and the switch architecture contains customized hard ware to separate data from control and improve switch throughput. The location of our active switches within the system yields ....

M. E. Fiuczynski and B. N. Betshad. SPINE - A Safe Programmable and Integrated Network Environment. In 16th Symposium on Operating System Principles, October 1997.

....be used in a subset of the MMLite application space, but the programming model and other limitations are probably not well suited for most applications outside the smart card domain . Similar models are also implemented by TinyOS [9] which requires a special purpose network protocol, and by SPINE [6]. A special purpose network protocol necessitates proxy computers for communication with the rest of the world , departing from the goal of ubiquitous communication. SPINE offers extensibility through Modula3. Windows for Smart Cards, like MMLite, has Visual Basic scripting. CORBA [14] forces ....

Mark Fiuczynski, Richard Martin, Tsutomu Owa, Brian Bershad. SPINE: A Safe Programmable and Integrated Network Environment. Eight ACM SIGOPS European Workshop, September 1998, Sintra, Portugal.

....substantial computing capabilities. Intelligent devices have the potential to mitigate the current I O bottleneck by preprocessing data and restructuring data during device idle cycles [9] However, such devices are failing to reach their full potential due to a lack of support in system software [6]. The Magi device interface is an extension of the Mona le system that enables transformations to migrate out of the le system to an intelligent peripheral device. As a result, a host system can push operations onto a device capable of processing data locally. Both kernel and user space ....

Marc E. Fiuczynski, Richard P. Martin, Tsutomu Owa, and Brian N. Bershad. SPINE: A safe programmable and integrated network environment. In Proc. of the Eighth ACM SIGOPS European Workshop, Sintra, Portugal, September 1998. ACM SIGOPS.

....sender based flow control [7] Our work differs from each of these projects in that we focus on functionality that is higher level than the network protocol layer. The SPINE system from the University of Washington provides a safe and extensible environment for programming network processors [11, 12]. In contrast, our work demonstrates the benefits and tradeoffs of moving memory management functionality to a network processor. We believe that the implementation and debugging of our prototype would have benefited from the SPINE framework. 2. Background and design of GMS NP GMS NP ....

M. E. Fiuczynski, R. P. Martin, T. Owa, and B. N. Bershad. SPINE - a safe programmable and integrated network environment. Eighth ACM SIGOPS European Workshop, September 1998.

....may reside on the main board or the peripheral device itself. Each IOP runs its own embedded operating system tailored for the device. IOP performance is limited only by processor speed and memory availability. Both these limitations are artificial and will yield to decreasing hardware cost. SPINE [20] is touted as a Network Operating System. The SPINE runtime resides in the host kernel while SPINE extension written in Modula 3 are downloaded to a Myrinet network interface. As proof that the concept is viable, two applications video server and IP router are implemented with impressive ....

Fiuczynski, M, and Bershad, B, SPINE - A safe programmable and integrated network environment, SOSP 16 Works in Progress, 1997.

....rst principle has already established that the ability to download operations to a device is a necessity. However, downloading application speci c operations allows even more exibility. Several systems have shown that application speci c customization leads to signi cant performance improvements [10, 5, 1]. Unfortunately, due to security concerns, many extensible systems only let privileged users implement extensions [19, 7, 11] This limits the advantages of intelligent devices by preventing ordinary, unprivileged applications from customizing the system. Furthermore, numerous well documented ....

....write, ioctl, etc. As a result, the Magi system has little cost of adoption while providing many bene ts of extensibility. Our current work focuses primarily on the bene ts of intelligent disk drives, yet al..so has great potential for emulating other devices, such as intelligent network adapters [5, 15]. 4 Related Work The concept of embedding intelligence into devices it not new and many familiar devices are already intelligent. Unfortunately, a general programming model to leverage intelligent devices is still lacking because each new device typically introduces a new specialized interface. ....

[Article contains additional citation context not shown here]

Marc E. Fiuczynski, Richard P. Martin, Tsutomu Owa, and Brian N. Bershad. SPINE - a safe programmable and integrated network environment. Eight ACM SIGOPS European Workshop, September 1998.

....set of built in features. However, experience has shown [10] that in the interest of reducing host overhead, interrupts, and I O bus transfers, it may be beneficial to perform some protocol processing within the network interface itself, for example on a dedicated network co processor [5]. Such a system could be used to implement a multicast tree directly on the NI, allowing data to be retransmitted down branches of the tree without intervention of the user application, eliminating overheads for I O bus transfer and context switch. Another potential application is packet specified ....

....also allows users to download code into the kernel. SPIN s networking architecture, Plexus, runs user protocol code within the kernel in an interrupt handler. Extensions are written in Modula 3 [14] and the compiler that generates the extensions is trusted to generate non malicious code. SPINE [5] extends the the ideas of SPIN to the network interface, and is the system most similar to U Net SLE in design and scope. Underlying SPINE is a Modula 3 runtime executing on the NI, the current prototype implementation of which uses the Myrinet interface. SPINE differs from U Net SLE in several ....

M. E. Fiuczynski and B. N. Bershad. "SPINE - A safe programmable and integrated network environment." SOSP 16 Works in Progress, 1997.

....and communication systems [2, 7, 19, 26] has demonstrated the fact that a single set of system primitives cannot easily satisfy the requirements of every user provided application program. One of the proposed solutions is to customize the application interaction with the network interface [8, 16, 17]. The research reported here goes further and considers customizing the interaction of the application with the entire network, viewed as a single entity. The DVCM architecture provides two mechanisms with which applications can customize their interactions with the network. First, applications ....

M. E. Fiuczynski and B. N. Bershad. SPINE - A Safe Programmable and Integrated Network Environment. Proceedings of the Work In Progress session of the 16th ACM Symposium on Operating Systems Principles, Oct. 1997.

....host overhead, interrupts, and I O bus transfers, it may be beneficial to perform some protocol processing 0 For more information on this project, please see http: www.cs.berkeley.edu mdw projects unet sle . within the network interface itself, for example on a dedicated network co processor [5]. Such a system could be used to implement a multicast tree directly on the NI, allowing data to be retransmitted down branches of the tree without intervention of the user application, overheads for I O bus transfer, and process or thread context switch. Another potential application is ....

....features mesh well with the U Net model of protected user level access to the network interface. An unsafe language without some external safety mechanism (such as Software Fault Isolation [29] or Proof Carrying Code [13] requires blindly trusting the compiler that generated the code (as in SPINE [5], which requires the compiler to sign downloaded code) The Java sandbox, as enforced by the bytecode verifier and runtime checks, protects applets from one another. Combined with resource consumption limits enforced by the runtime system, these safety features provide a strong guarantee that a ....

[Article contains additional citation context not shown here]

M. E. Fiuczynski and B. N. Bershad. "SPINE - A safe programmable and integrated network environment." SOSP 16 Works in Progress, 1997.

....each application in isolation. While scenarios exist in which an entire machine is dedicated to a single application, a more common scenario includes machines whose normal workload includes several concurrent applications. We are currently porting the SPINE programmable NI operating system [2, 3] to our simulation ip4lookup 0.0E 00 5.0E 06 1.0E 07 1.5E 07 2.0E 07 2.5E 07 3.0E 07 3.5E 07 4.0E 07 4.5E 07 5.0E 07 1 2 3 4 5 6 7 8 # of SMT thread contexts message per second SMT 500mhz SMT 400mhz SMT 300mhz SMT 200mhz SMT 100mhz 1Gbps 10Gbps MD5 0.0E 00 2.0E 04 ....

M.E. Fiuczynski, R.P. Martin, T. Oha, and B.N. Bershad. SPINE - A Safe Programmable and Integrated Network Environment. Proceedings of the Eight ACM SIGOPS European Workshop, pp. 8. Sintra, Portugal, September 1998.

.... not directly related to multimedia, range from packet filtering (e.g. Lazy Receive Processing [2] cluster based storage management (e.g. Petal [3] to distributed memory management systems (e.g. Global Memory [4] Our strategy is to provide an extensible runtime environment, called SPINE [9], for programmable network interface cards. Extensibility is important, as we cannot predict the types of applications that may want to process directly on the network interface. SPINE extends the fundamental ideas in SPIN [1] type safe code (called extensions) downloaded into a trusted ....

M.E. Fiuczynski. SPINE: A Safe Programmable and Integrated Network Environment. Overview Information available from: http://www.cs.washington.edu/homes/mef/research/spine

No context found.

M. Fiuczynski, R. Martin, T. Owa, and B. Bershad. Spine: A safe programmable and integrated network environment. In Eight ACM SIGOPS European Workshop, September 1998.

No context found.

Fiuczynski M. and Bershad B. SPINE: A safe programmable and integrated network environment. In Proceedings of the Eighth ACM SIGOPS Workshop, 1998.

No context found.

M. E. Fiuczynski, R. P. Martin, T. Owa, and B. N. Bershad. SPINE: A Safe Programmable and Integrated Network Environment. In Proceedings of the 8th ACM SIGOPS European Workshop on Support for Composing Distributed Applications, pages 7--12, Sintra, Portugal, September 1998.

No context found.

Fiuczynski M. and Bershad B. SPINE: A safe programmable and integrated network environment. In Proceedings of the Eighth ACM SIGOPS Workshop, 1998.

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