Difference between revisions of "Main Page/hybrid prog"
From Nekcem
Jump to navigationJump to search| Line 11: | Line 11: | ||
**#* introduction of locality-oriented concepts? | **#* introduction of locality-oriented concepts? | ||
**#* efforts in OpenMP 3.0 ? | **#* efforts in OpenMP 3.0 ? | ||
| − | |||
**# PGAS languages | **# PGAS languages | ||
**#* already support a notation of locality in a shared namespace | **#* already support a notation of locality in a shared namespace | ||
**#* UPC/CAF need to relax strictly SPMD execution model | **#* UPC/CAF need to relax strictly SPMD execution model | ||
| − | |||
**# Sequoia | **# Sequoia | ||
**#* support a strong notation of vertical locality | **#* support a strong notation of vertical locality | ||
Revision as of 11:24, 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 ?
- 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
- OpenMP
- MPI for inter-node prog, since # notes and inter-node concerns not expected to change dramatically
- unified/holistic: __ ?
- a single notation for inter- and intra-node programming?
