Even though the ofi component doesn't do any routing itself, the rest of the code base (e.g., grpcomm) needs to know what routing module this component is using. So set it to the "direct" module, and don't allow ofi to be used if that module isn't available.

Signed-off-by: Ralph Castain <[email protected]>

Author: Ralph Castain

orte/mca/rml/ofi/rml_ofi_component.c

@@ -951,7 +951,16 @@ static orte_rml_base_module_t* make_module( int ofi_prov_id)
     memcpy(mod, &orte_rml_ofi, sizeof(orte_rml_ofi_module_t));
     /*  setup the remaining data locations in mod, associate conduit with ofi provider selected*/
     mod->cur_transport_id = ofi_prov_id;
-
+    /* we always go direct to our target peer, so set the routed to "direct" */
+    mod->api.routed = orte_routed.assign_module("direct");
+    if (NULL == mod->api.routed) {
+        /* we can't work */
+        opal_output_verbose(20,orte_rml_base_framework.framework_output,
+                    "%s - Failed to get direct routed support, returning NULL ",
+                    ORTE_NAME_PRINT(ORTE_PROC_MY_NAME));
+        free(mod);
+        return NULL;
+    }
     return (orte_rml_base_module_t*)mod;
 }