MPI-2 implementation on Fujitsu generic message passing kernel
SC '99 Proceedings of the 1999 ACM/IEEE conference on Supercomputing
The implementation of MPI-2 one-sided communication for the NEC SX-5
Proceedings of the 2000 ACM/IEEE conference on Supercomputing
Single sided MPI implementations for SUN MPIr
Proceedings of the 2000 ACM/IEEE conference on Supercomputing
Implementing MPI's One-Sided Communications for WMPI
Proceedings of the 6th European PVM/MPI Users' Group Meeting on Recent Advances in Parallel Virtual Machine and Message Passing Interface
Exploiting Transparent Remote Memory Access for Non-Contiguous- and One-Sided-Communication
IPDPS '02 Proceedings of the 16th International Parallel and Distributed Processing Symposium
Protocols and Strategies for Optimizing Performance of Remote Memory Operations on Clusters
IPDPS '02 Proceedings of the 16th International Parallel and Distributed Processing Symposium
Improved MPI All-to-all Communication on a Giganet SMP Cluster
Proceedings of the 9th European PVM/MPI Users' Group Meeting on Recent Advances in Parallel Virtual Machine and Message Passing Interface
An evaluation of implementation options for MPI one-sided communication
PVM/MPI'05 Proceedings of the 12th European PVM/MPI users' group conference on Recent Advances in Parallel Virtual Machine and Message Passing Interface
| Hi-index | 0.00 |
We describe and evaluate an implementation of the MPI-2 one-sided communications on a Giganet SMP Cluster. The cluster runs under Linux with our own port of MPICH 1.2.1, a well-known, portable, non-threaded MPI implementation, to the Virtual Interface Provider Library (VIPL). We call this implementation MPI/VIA. The one-sided communications part was adapted from MPI/SX, a full MPI-2 implementation for the NEC SX-5 vector-parallel supercomputer. We evaluate the performance of the one-sided communications by comparing to point-to-point communication. For applications that can be implemented naturally in both the one-sided and the point-to-point model, the MPI/VIA implementation is such that the user is not penalized by choosing one model over the other.