a2919174d0
Multiple conduits can exist at the same time, and can even point to the same base transport. Each conduit can have its own characteristics (e.g., flow control) based on the info keys provided to the "open_conduit" call. For ease during the transition period, the "legacy" RML interfaces remain as wrappers over the new conduit-based APIs using a default conduit opened during orte_init - this default conduit is tied to the OOB framework so that current behaviors are preserved. Once the transition has been completed, a one-time cleanup will be done to update all RML calls to the new APIs and the "legacy" interfaces will be deleted. While we are at it: Remove oob/usock component to eliminate the TMPDIR length problem - get all working, including oob_stress
30 строки
800 B
Bash
30 строки
800 B
Bash
# -*- shell-script -*-
|
|
#
|
|
# Copyright (c) 2013-2014 Intel, Inc. All rights reserved
|
|
#
|
|
# Copyright (c) 2014-2015 Cisco Systems, Inc. All rights reserved.
|
|
# $COPYRIGHT$
|
|
#
|
|
# Additional copyrights may follow
|
|
#
|
|
# $HEADER$
|
|
#
|
|
|
|
# MCA_orte_rml_ofi_POST_CONFIG(will_build)
|
|
# ----------------------------------------
|
|
# Only require the tag if we're actually going to be built
|
|
|
|
# MCA_mtl_ofi_CONFIG([action-if-can-compile],
|
|
# [action-if-cant-compile])
|
|
# ------------------------------------------------
|
|
AC_DEFUN([MCA_orte_rml_ofi_CONFIG],[
|
|
AC_CONFIG_FILES([orte/mca/rml/ofi/Makefile])
|
|
|
|
# ensure we already ran the common libfabric config
|
|
AC_REQUIRE([MCA_opal_common_libfabric_CONFIG])
|
|
|
|
AS_IF([test "$opal_common_libfabric_happy" = "yes"],
|
|
[$1],
|
|
[$2])
|
|
])dnl
|