Difference between revisions of "Main Page/hybrid prog"
From Nekcem
Jump to navigationJump to searchLine 7: | Line 7: | ||
*** purer one-sided communications; active messages | *** purer one-sided communications; active messages | ||
*** asynchronous collectives | *** asynchronous collectives | ||
− | |||
** something else for intra-node | ** something else for intra-node | ||
**# OpenMP | **# OpenMP |
Revision as of 11:23, 31 January 2011
This is the document page for hybrid programming plan for NekCEM.
Approaches {some notes taken from DOE Exascale workshop}
- hybrid/evolutionary: MPI+ ___ ?
- MPI for inter-node prog, since # notes and inter-node concerns not expected to change dramatically
- support for hybrid programming/interoperability
- purer one-sided communications; active messages
- asynchronous collectives
- something else for intra-node
- OpenMP
- introduction of locality-oriented concepts?
- efforts in OpenMP 3.0 ?
- OpenMP
- MPI for inter-node prog, since # notes and inter-node concerns not expected to change dramatically
- PGAS languages
- already support a notation of locality in a shared namespace
- UPC/CAF need to relax strictly SPMD execution model
- PGAS languages
- Sequoia
- support a strong notation of vertical locality
- Sequoia
- unified/holistic: __ ?
- a single notation for inter- and intra-node programming?