1998
DOI: 10.1007/3-540-64359-1_682
|View full text |Cite
|
Sign up to set email alerts
|

Multiparadigm, multilingual interoperability: Experience with converse

Abstract: Abstract. The Converse run-time framework was designed with dual objectives: that of supporting quick development of portable run-time systems for new parallel programming paradigms, and that of permitting interoperability b e t ween multi-paradigm modules in a single application. This paper reports on the re nements made to the original Converse model since its inception almost two y ears ago, and assesses our experience in using Converse to satisfy the above objectives. A brief overview of the motivation and… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
10
0

Year Published

1999
1999
2008
2008

Publication Types

Select...
3
2
2

Relationship

0
7

Authors

Journals

citations
Cited by 13 publications
(10 citation statements)
references
References 13 publications
0
10
0
Order By: Relevance
“…NAMD is implemented using the Converse [8] runtime system, and the major components of NAMD are written in Charm++ [10], a parallel version of C++. Converse supplies several important capabilities for parallel applications.…”
Section: Runtime Support For Dynamic Computationmentioning
confidence: 99%
“…NAMD is implemented using the Converse [8] runtime system, and the major components of NAMD are written in Charm++ [10], a parallel version of C++. Converse supplies several important capabilities for parallel applications.…”
Section: Runtime Support For Dynamic Computationmentioning
confidence: 99%
“…Eventually, a limit is reached in which the communication overhead exceeds the useful computational work, at which point additional processors can no longer be used effectively. In this article, we introduce a new parallelization strategy for CPAIMD based on the concept of virtualization , as embodied in the Charm++ runtime system 47, 48. Virtualization simply means that computational work to be done is divided into individual concurrent entities or “threads,” also called virtual processors (VPs), that are then mapped onto the physical processors by the runtime system (rather than by the programmer).…”
Section: Introductionmentioning
confidence: 99%
“…Converse [19] provides the tools for implementing different paradigms in a message-driven system with objectbased VPs. Apart from providing a scheduler on each processor, Converse also provides a messaging framework with primitives for point-to-point communication and multicasts, and methods for handling a message on the receiving processor.…”
Section: A Multi-paradigm Runtime Systemmentioning
confidence: 99%
“…Our approach relies on Converse [19], an ARTS which fully realizes the tightly coupled interoperability of multiple paradigms. Converse meets many of the goals mentioned in a recent report from Berkeley [3], including the need for models to be independent of the number of processors, and it alleviates cognitive load on programmers by performing automatic resource management.…”
Section: Introductionmentioning
confidence: 99%