Difference between revisions of "Main Page/hybrid prog"
From Nekcem
Jump to navigationJump to searchLine 1: | Line 1: | ||
This is the document page for hybrid programming plan for [http://www.mcs.anl.gov/~mmin/nekcem.html NekCEM]. | This is the document page for hybrid programming plan for [http://www.mcs.anl.gov/~mmin/nekcem.html NekCEM]. | ||
− | ==Approaches { | + | ==Approaches {some notes taken from DOE Exascale workshop}== |
* hybrid/evolutionary: MPI+ ___ ? | * hybrid/evolutionary: MPI+ ___ ? | ||
− | ** MPI for inter-node prog, something else for intra- | + | ** 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 ? | ||
+ | |||
+ | **# PGAS languages | ||
+ | **#* already support a notation of locality in a shared namespace | ||
+ | **#* UPC/CAF need to relax strictly SPMD execution model | ||
+ | |||
+ | **# Sequoia | ||
+ | **#* support a strong notation of vertical locality | ||
+ | |||
* unified/holistic: __ ? | * unified/holistic: __ ? | ||
** a single notation for inter- and intra-node programming? | ** a single notation for inter- and intra-node programming? |
Revision as of 11:21, 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
- MPI for inter-node prog, since # notes and inter-node concerns not expected to change dramatically
- something else for intra-node
- OpenMP
- introduction of locality-oriented concepts?
- efforts in OpenMP 3.0 ?
- OpenMP
- something else for intra-node
- 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?