From 056daa05bf1502de9ccaa9824f9c340cf7b43f22 Mon Sep 17 00:00:00 2001 From: Howard Pritchard Date: Thu, 22 Jan 2015 06:53:45 -0800 Subject: [PATCH] btl/ugni: use PMIX_GLOBAL for modex_send in ugni Using PMIX_REMOTE is not the right thing for ugni BTL when its possible that spawned ranks end up on the same node as some of the spawnee ranks. --- opal/mca/common/ugni/common_ugni.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/opal/mca/common/ugni/common_ugni.c b/opal/mca/common/ugni/common_ugni.c index 4860cd6b82..d7812b64c7 100644 --- a/opal/mca/common/ugni/common_ugni.c +++ b/opal/mca/common/ugni/common_ugni.c @@ -190,7 +190,12 @@ static int opal_common_ugni_send_modex (int my_cdm_id) msg_offset += modex_size; } - OPAL_MODEX_SEND(rc, PMIX_ASYNC_RDY, PMIX_REMOTE, + /* + * need global for edge cases like MPI_Comm_spawn support with + * new ranks started on the same nodes as the spawnee ranks, etc. + */ + + OPAL_MODEX_SEND(rc, PMIX_ASYNC_RDY, PMIX_GLOBAL, &opal_common_ugni_component, modex_msg, total_msg_size);