Compaq, Intel, and Microsoft Corporations. Virtual Interface Architecture. Version 1.0, December 1997. Available from www.viarch.org.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....communication and scheduling overhead, we can also implement zero copy (or low copy, if we desire fault tolerant communication) communication. As a result, our approach to communication bu ering can achieve performance comparable to user level network interfaces (i.e. OS bypass protocols) [5, 22, 2, 17, 18] without using specialized HW. 3.2 Strobing The uneven resource utilization and the periodic, bursty communication patterns generated by many parallel applications can be exploited to perform a total exchange of information and synchronizing the processors at regular intervals with little ....

Compaq, Intel, and Microsoft. The Virtual Interface Architecture (VIA) Specication. available at http://www.viarch.org.

....[25] and U Net [26] which are highly optimized communication layers for Ethernet and Fast Ethernet networks, provide some form of reliability and ow control but force the upper layers to deal with preallocated xed sized bu ers for message manipulation. The Virtual Interface Architecture (VIA [8]) provides an abstract speci cation of the interactions between the operating system and the user level communication level. A Virtual Interface (VI) consists of a pair of message queues: a send queue and a receive queue. The user program posts emission or reception requests on the message queues ....

....be directly used by regular user level applications. This interface is especially targeted at RPC based multithreaded environments such as PM 2 or Nexus. In this context, it is intended to bridge the gap between the functionalities provided by low level network protocols (such as BIP [23] or VIA [8]) and the requirements of high level abstractions (such as the RPC mechanism) Madeleine has been designed to allow the upper software layers (i.e. inside the multithreaded environment) to avoid extra copies of transmitted data. At the lowest level, this cooperation is realized using up calls on ....

[Article contains additional citation context not shown here]

Compaq, Intel, and Microsoft Corporations. Virtual Interface Architecture. Version 1.0, December 1997. Available from www.viarch.org.

....Out of these projects the industry driven standard VIA[6] was created, initially by Intel, Compaq and Microsoft. This standard specifies an interface between the high speed network cards and the system. Later Intel has published some enhancements and some suggestions for the implementation[7]. The structure of the VIA is shown in Figure 1. For the creation of a new MPI library the two important parts of this structure are the VI User Agent and the VI Kernel Agent. The User Agent provides the user level part of the interface to the network(card) whereas the Kernel Agent is a kernel ....

....of the operation. The VIA requires to identify memory used for data transfer. For this identification the memory has to be registered before the transfer. The registration of the memory works with so called protection tags 4 . As already noted the mem 2 This term was introduced in [7]. 3 A data structure that describes a data transfer request. 4 Usually, a process uses a unique protection tag which is created after opening the VIA environment. This protection tag is bounded to each VI ory registration (as well as the deregistration) is realized by courtesy of the VI Kernel ....

[Article contains additional citation context not shown here]

Intel Cooperation. Virtual Interface Architecture (VI) Implementation Guide, May 1998.

....can properly set our expectations for application performance. 5. 1 Myrinet performance Myrinet offers 2 different interfaces to the system; the usual networking interface via the kernel running protocols such as TCP and UDP, and a user level interface similar to U Net [2] or the VIA standard [4]. Gigabit networking requires a low overhead interface in order to get gigabit performance; there have been many demonstrations of 700 to 900 gigabit sustained transfers using Myrinet with various user level interfaces. However, we have yet to write an interface between the Legion networking code ....

Intel Corporation. The virtual interface architecture. http://www.intel.com/procs/SERVERS/isv/vi/vi2/index.htm.

....[17] they are called user s context interfaces: since system calls are quite expensive, communications try to avoid them. Messages are directly sent from the user space level memory to the network interface board without any intervention of the operating system. Recently, an industrial standard [4] for this kind of interfaces has been proposed. However, they act at a low level and their use by an average programmer is not straightforward. Higher level interfaces have been developed, such as MPI 1 http: www.sandia.gov ASCI TFLOP HomePage. html 2 ....

Compaq, Intel and Microsoft corporations. Virtual Interface Architecture. Version 1.0, December 1997. Available from http://www.viarch.org.

....24] These include a superstep profiling tool, an advanced call graph performance tuning aid with a sophisticated graphical user interface, a BSP performance signature tool, and various BSP benchmarking tools. Parallel debugging support tools are also included. The recently announced VIA standard [3] provides a network level Application Programming Interface for scalable clusters. Although targeted at a lower level than BSPlib and aiming a wider range of programming styles, VIA has a number of features in common with BSPlib. As commodity VIA hardware becomes available, it will be ....

COMPAQ, INTEL, AND MICROSOFT. The Virtual Interface Architecture (VIA) Specification. Version 1.0. Available at http://www.viarch.org, Dec. 1997.

No context found.

Compaq, Intel, and Microsoft Corporations. Virtual Interface Architecture. Version 1.0, December 1997. Available from www.viarch.org.

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