[Mpi3-hybridpm] [MPI Forum] #212: MPI3 Hybrid Programming: multiple endpoints per collective, option 5
MPI Forum
mpi-22 at lists.mpi-forum.org
Thu Jan 7 07:49:31 CST 2010
#212: MPI3 Hybrid Programming: multiple endpoints per collective, option 5
----------------------------------------------------------+-----------------
Reporter: dougmill@… | Owner: dougmill@…
Type: Enhancements to standard | Status: new
Priority: Not ready / author rework | Milestone: 2010/01/19 Atlanta, USA
Version: MPI 3.0 | Keywords:
Implementation: Unnecessary | Author_bill_gropp: 0
Author_rich_graham: 0 | Author_adam_moody: 0
Author_torsten_hoefler: 0 | Author_dick_treumann: 0
Author_jesper_larsson_traeff: 0 | Author_george_bosilca: 0
Author_david_solt: 0 | Author_bronis_de_supinski: 0
Author_rajeev_thakur: 0 | Author_jeff_squyres: 0
Author_alexander_supalov: 0 | Author_rolf_rabenseifner: 0
----------------------------------------------------------+-----------------
Comment(by dougmill@…):
The would probably require every agent to periodically call the progress
engine, even if it is not doing communication. For programs that have
well-defined/delineated compute/communicate phases this is not too much of
a problem. For more-asynchronous programs it would be a bit less natural
to have to periodically make calls into the progress engine - and have the
frequency of those calls affect the progress of other agents. This might
be helped by having additional threads which make progress independently
of the program threads, but that requires more threads (or leaves less
threads for the computation).
--
Ticket URL: <https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/212#comment:1>
MPI Forum <https://svn.mpi-forum.org/>
MPI Forum
More information about the mpiwg-hybridpm
mailing list