Myricom Inc., Myrinet User's Guide, http://www.myri.com, 1996. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
PARNASS: Porting Gigabit-LAN components to a workstation cluster - Griebel, Zumbusch (1997) (2 citations) (Correct)
....of message passing libraries, while some of the software layers to implement them become obsolete. 2.4.1. Message Passing APIs There are many efforts to develop message passing libraries for the Myrinet. The original programming interface designed for the Myrinet is the API by Myricom [Myr96] It provides a message passing semantic for single packet messages up to a maximum transfer unit (MTU) of 8132 bytes. Routing is done by the NIC processors, which dynamically determine the network topology. The API supports asynchronous communication with a limited amount of buffering. The ....
....some even for Power PCs and Windows NT on Intel and DEC Alpha based machines. However, no such drivers had been written for Silicon Graphics workstations yet. We will describe some considerations of the port. 4.1. Myricom API First we describe the port of the Myricom API (see chapter 2.4. 1 and [Myr96] to Parnass. We will encounter some performance problems, which we will relate to the hardware PCI bus implementation in use. 4.1.1. Device Driver. The new kernel device driver registers for the Myrinet NIC vendor and adapter numbers, see [ET88, Cor96] The driver is loaded in case the kernel ....
Myricom, Inc. Myrinet User's Guide, 1996.
PARNASS: Porting Gigabit-LAN components to a workstation cluster - Griebel, Zumbusch (1997) (2 citations) (Correct)
....of message passing libraries, while some of the software layers to implement them become obsolete. 6 2.4.1. Message Passing APIs. There are many efforts to develop message passing libraries for the Myrinet. The original programming interface designed for the Myrinet is the API by Myricom [Myr96] It provides a message passing semantic for single packet messages up to a maximum transfer unit (MTU) of 8132 bytes. Routing is done by the NIC processors, which dynamically determine the network topology. The API supports asynchronous communication with a limited amount of buffering. The ....
....for Power PCs and Windows NT on Intel and DEC Alpha based machines. However, no such drivers had been written for Silicon Graphics workstations so far. We will describe some considerations of the port we did. 4.1. Myricom API. First we describe the port of the Myricom API (see chapter 2.4. 1 and [Myr96] to Parnass. We implemented kernel device drivers for SGI IRIX and we ported the Myricom API to the SGI platform. We encountered several problems such as little big endian adressing, many memory copy operations, cache coherence problems of DMA transfers and a lack of API protocol reliability. ....
Myricom, Inc. Myrinet User's Guide, 1996.
BDM: A Multiprotocol Myrinet Control Program and Host .. - Henley, Doss.. (1997) (3 citations) (Correct)
....and active networking experiments. Robust reliability and low processor overhead distinguish this effort from others. 1 Introduction The BDM (BullDog 1 MCP) software consists of a set of host library routines and a Myrinet Control Program (MCP) for the Myricom LANai network processor [1, 15]. BDM was designed to provide a capable yet simple MCP useful for experiments with new protocols and different levels of service in support of systems such as MPI [7] and Packetway [8] Also, we want to provide the lowest latency and highest bandwidth possible consistent with robust reliability. ....
Myricom Inc. Myrinet User's Guide, 1997. http://www.myri.com/scs/documentation/mug/.
Informatica 29 (2005) 219--226 219 - System Resource Utilization (Correct)
No context found.
Myricom Inc., Myrinet User's Guide, http://www.myri.com, 1996.
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