Towards MPI progression layer elimination with TCP and SCTP

Authors:
Brad Penoff;Alan Wagner
Affiliations:
University of British Columbia, Vancouver, BC, Canada;University of British Columbia, Vancouver, BC, Canada
Venue:
IPDPS'06 Proceedings of the 20th international conference on Parallel and distributed processing
Year:
2006

Citing 7
Cited 1

A high-performance, portable implementation of the MPI message passing interface standard

Parallel Computing
Components and interfaces of a process management system for parallel programs

Parallel Computing - Clusters and computational grids for scientific computing
UNIX Network Programming, Vol. 1

UNIX Network Programming, Vol. 1
Connection-less TCP

IPDPS '05 Proceedings of the 19th IEEE International Parallel and Distributed Processing Symposium (IPDPS'05) - Workshop 9 - Volume 10
Comparing Ethernet and Myrinet for MPI communication

LCR '04 Proceedings of the 7th workshop on Workshop on languages, compilers, and run-time support for scalable systems
SCTP versus TCP for MPI

SC '05 Proceedings of the 2005 ACM/IEEE conference on Supercomputing
The design and implementation of an asynchronous communication mechanism for the MPI communication model

CLUSTER '04 Proceedings of the 2004 IEEE International Conference on Cluster Computing

Using SCTP to hide latency in MPI programs

IPDPS'06 Proceedings of the 20th international conference on Parallel and distributed processing

Quantified Score

Hi-index	0.00

Visualization

Abstract

MPI middleware glues together the components necessary for execution. Almost all implementations have a communication component also called a message progression layer that progresses outstanding messages and maintains their state. The goal of this work is to thin or eliminate this communication component by pushing the functionality down onto the standard IP stack in order to take advantage of potential advances in commodity networking. We introduce a TCP-based design that successfully eliminates the communication component. We discuss how this eliminated TCP-based design doesn't scale and show a more scalable design based on the Stream Control Transmission Protocol (SCTP) that has a thinned communication component. We compare the designs showing why SCTP one-to-many sockets in their current form can only thin the communication component. We show what additional features would be required of SCTP to enable a practical design with a fully eliminated communication component.