Single Sided Communications in Multi-protocol MPI

Mourão, Fernando Elson; Booth, Stephen

doi:10.1007/3-540-45255-9_26

Cited by 5 publications

(1 citation statement)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…These data-transfer functions must be used together with one of three synchronization mechanismsfence, post-start-complete-wait, and lock-unlock-as shown in Figure 1. Many MPI implementations, including all vendor MPIs, support one-sided communication, with varying levels of optimization [1,2,4,6,7,9,10,12,14,15]. Nonetheless, Gabriel et al [3] found that, because of the synchronization overhead in one-sided communication, regular point-to-point communication performs better than one-sided communication in five MPI implementations: NEC, Hitachi, IBM, Sun, and LAM.…”

Section: Introductionmentioning

confidence: 99%

An Evaluation of Implementation Options for MPI One-Sided Communication

Gropp

Thakur

2005

Recent Advances in Parallel Virtual Machine and Message Passing Interface

View full text Add to dashboard Cite

Abstract. MPI defines one-sided communication operations-put, get, and accumulate-together with three different synchronization mechanisms that define the semantics associated with the initiation and completion of these operations. In this paper, we analyze the requirements imposed by the MPI Standard on any implementation of one-sided communication. We discuss options for implementing the synchronization mechanisms and analyze the cost associated with each. An MPI implementer can use this information to select the implementation method that is best suited (has the lowest cost) for a particular machine environment. We also report on experiments we ran on a Linux cluster and a Sun SMP to determine the gap between the performance that could be achievable and what is actually achieved with MPI.

show abstract