Merge pull request #9480 from wzamazon/evloop_once

Author: bosilca

ompi/runtime/ompi_mpi_init.c

@@ -1009,7 +1009,8 @@ int ompi_mpi_init(int argc, char **argv, int requested, int *provided,
        CPU utilization for the remainder of MPI_INIT when we are
        blocking on RTE-level events, but may greatly reduce non-TCP
        latency. */
-    opal_progress_set_event_flag(OPAL_EVLOOP_NONBLOCK);
+    int old_event_flags = opal_progress_set_event_flag(0);
+    opal_progress_set_event_flag(old_event_flags | OPAL_EVLOOP_NONBLOCK);
 #endif
 
     /* wire up the mpi interface, if requested.  Do this after the

opal/runtime/opal_progress.h

@@ -66,11 +66,19 @@ OPAL_DECLSPEC int opal_progress(void);
  * Control how the event library is called
  *
  * Adjust the flags argument used to call opal_event_loop() from
- * opal_progress().  The default argument is OPAL_EVLOOP_ONELOOP,
- * meaning that the call to opal_event_loop() will block pending
- * events, but may block for a period of time.
+ * opal_progress().  The default argument is
  *
- * @param flags     One of the valid vlags argument to
+ *               OPAL_EVLOOP_NONBLOCK | OPAL_EVLOOP_ONCE
+ *
+ * OPAL_EVLOOP_NONBLOCK means that if there is no active events,
+ * opal_event_loop() should return immediately (instead of
+ * waiting for active events).
+ *
+ * OPAL_EVLOOP_ONCE means opal_event_loop() should onlyrun one
+ * iteration, which includes poll the event queue and process
+ * the active events.
+ *
+ * @param flags     One of the valid flags argument to
  *                  opal_event_loop().
  * @return          Previous value of flags used to call
  *                  opal_event_loop().