[Mpi3-hybridpm] [MPI Forum] #211: MPI3 Hybrid Programming: multiple endpoints per collective, option 4
MPI Forum
mpi-22 at lists.mpi-forum.org
Thu Jan 7 08:03:15 CST 2010
#211: MPI3 Hybrid Programming: multiple endpoints per collective, option 4
----------------------------------------------------------+-----------------
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@…):
This would probably require a barrier as part of the
MPI_Endpoint_attach_helper call, and including the master thread. since
the master would not want to start communications until all helper threads
were available. Or, perhaps the master knows how many threads to expect,
and can give that information to MPI such that the implementation can just
spawn the extra work and it will complete when the other threads attach as
helpers. But, this would also probably require knowledge of exactly which
endpoints are expected to become helpers, since those specific endpoints
would be the targets for spawned work.
--
Ticket URL: <https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/211#comment:3>
MPI Forum <https://svn.mpi-forum.org/>
MPI Forum
More information about the mpiwg-hybridpm
mailing list