A safe vertex

Edward W. Felten, Steve W. Otto

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

The VERTEX message passing system provided with NCUBE hypercubes is unsafe. The system can fail under high message loads. We have implemented a message passing system with the same "look and feel" as VERTEX but which is instead based upon the crystal-trouter running at clock interrupt time. The system is written mostly in C with a few bits of assembly code to run the DMA devices. This implies that safety checks (are the buffers full?) and complex error handling mechanisms can be easily implemented at the C level. A first version works, is safe, and is faster than VERTEX in the high volume limit, slower in the low volume case. At the very least, this system will be interesting for high message traffic applications, such as disk backup.

Original languageEnglish (US)
Title of host publicationProceedings of the 3rd Conference on Hypercube Concurrent Computers and Applications
Subtitle of host publicationArchitecture, Software, Computer Systems, and General Issues, C3P 1988
EditorsGeoffrey Fox
PublisherAssociation for Computing Machinery, Inc
Pages560-562
Number of pages3
ISBN (Electronic)0897912780, 9780897912785
DOIs
StatePublished - Jan 1 1988
Event3rd Conference on Hypercube Concurrent Computers and Applications, C3P 1988 - Pasadena, United States
Duration: Jan 19 1988Jan 20 1988

Publication series

NameProceedings of the 3rd Conference on Hypercube Concurrent Computers and Applications: Architecture, Software, Computer Systems, and General Issues, C3P 1988
Volume1

Other

Other3rd Conference on Hypercube Concurrent Computers and Applications, C3P 1988
Country/TerritoryUnited States
CityPasadena
Period1/19/881/20/88

All Science Journal Classification (ASJC) codes

  • Hardware and Architecture
  • Computer Graphics and Computer-Aided Design
  • Software
  • Computer Science Applications

Fingerprint

Dive into the research topics of 'A safe vertex'. Together they form a unique fingerprint.

Cite this