2006
DOI: 10.1177/1094342006064504
|View full text |Cite
|
Sign up to set email alerts
|

High Performance Remote Memory Access Communication: The Armci Approach

Abstract: This paper describes the Aggregate Remote Memory Copy Interface (ARMCI), a portable high performance remote memory access communication interface, developed oriinally under the U.S. Department of Energy (DOE) Advanced Computational Testing and Simulation Toolkit project and currently used and advanced as a part of the run-time layer of the DOE project, Programming Models for Scalble Parallel Computing. The paper discusses the model, addresses challenges of portable implementations, and demonstrates that ARMCI … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
54
0

Year Published

2007
2007
2022
2022

Publication Types

Select...
4
4
2

Relationship

1
9

Authors

Journals

citations
Cited by 92 publications
(54 citation statements)
references
References 10 publications
0
54
0
Order By: Relevance
“…As the number of partitions increases, every process has to communicate with only a small number of other processes. Therefore, the communi- cation costs are reduced by using one-sided point-to-point communication APIs provided by ARMCI [28].…”
Section: F Communication Between Processesmentioning
confidence: 99%
“…As the number of partitions increases, every process has to communicate with only a small number of other processes. Therefore, the communi- cation costs are reduced by using one-sided point-to-point communication APIs provided by ARMCI [28].…”
Section: F Communication Between Processesmentioning
confidence: 99%
“…For example, ARMCI (Aggregate Remote Memory Copy Interface) [21], [22] and Global Arrays (GA) [23]- [25] are ported based on such strategy. In such case, user cannot optimize translated MPI programs.…”
Section: One Sided Communication and Pgas Environmentsmentioning
confidence: 99%
“…The diagram illustrates the box management. Empty boxes (5,8,10,11,12) are not stored. The ibox vector associates the box number with each particle.…”
Section: Initial Data Distributionmentioning
confidence: 99%