2004-08-06 23:35:57 +04:00
|
|
|
#
|
2005-11-05 22:57:48 +03:00
|
|
|
# Copyright (c) 2004-2005 The Trustees of Indiana University and Indiana
|
|
|
|
# University Research and Technology
|
|
|
|
# Corporation. All rights reserved.
|
|
|
|
# Copyright (c) 2004-2005 The University of Tennessee and The University
|
|
|
|
# of Tennessee Research Foundation. All rights
|
|
|
|
# reserved.
|
2009-04-24 20:39:33 +04:00
|
|
|
# Copyright (c) 2004-2009 High Performance Computing Center Stuttgart,
|
2004-11-28 23:09:25 +03:00
|
|
|
# University of Stuttgart. All rights reserved.
|
2005-03-24 15:43:37 +03:00
|
|
|
# Copyright (c) 2004-2005 The Regents of the University of California.
|
|
|
|
# All rights reserved.
|
2014-03-28 22:24:32 +04:00
|
|
|
# Copyright (c) 2010-2014 Cisco Systems, Inc. All rights reserved.
|
2013-02-27 00:44:56 +04:00
|
|
|
# Copyright (c) 2010-2013 Los Alamos National Security, LLC.
|
2010-08-23 20:04:13 +04:00
|
|
|
# All rights reserved.
|
2004-11-22 04:38:40 +03:00
|
|
|
# $COPYRIGHT$
|
|
|
|
#
|
|
|
|
# Additional copyrights may follow
|
|
|
|
#
|
2004-08-06 23:35:57 +04:00
|
|
|
# $HEADER$
|
|
|
|
#
|
|
|
|
|
2004-08-07 01:40:23 +04:00
|
|
|
# A word of explanation...
|
|
|
|
#
|
|
|
|
# This library is linked against various MCA components because all
|
|
|
|
# shared-memory based components (e.g., mpool, ptl, etc.) need to
|
|
|
|
# share some common code and data. There's two cases:
|
|
|
|
#
|
|
|
|
# 1. libmca_common_sm.la is a shared library. By linking that shared
|
|
|
|
# library to all components that need it, the OS linker will
|
|
|
|
# automatically load it into the process as necessary, and there will
|
|
|
|
# only be one copy (i.e., all the components will share *one* copy of
|
|
|
|
# the code and data).
|
|
|
|
#
|
|
|
|
# 2. libmca_common_sm.la is a static library. In this case, it will
|
|
|
|
# be rolled up into the top-level libmpi.la. It will also be rolled
|
|
|
|
# into each component, but then the component will also be rolled up
|
|
|
|
# into the upper-level libmpi.la. Linkers universally know how to
|
|
|
|
# "figure this out" so that we end up with only one copy of the code
|
|
|
|
# and data.
|
2004-08-27 18:55:41 +04:00
|
|
|
#
|
|
|
|
# Note that building this common component statically and linking
|
|
|
|
# against other dynamic components is *not* supported!
|
2004-08-07 01:40:23 +04:00
|
|
|
|
2004-08-06 23:35:57 +04:00
|
|
|
# Header files
|
|
|
|
|
|
|
|
headers = \
|
2011-06-21 19:41:57 +04:00
|
|
|
common_sm.h
|
2004-08-06 23:35:57 +04:00
|
|
|
|
2004-08-27 18:55:41 +04:00
|
|
|
# Source files
|
2004-08-06 23:35:57 +04:00
|
|
|
|
2004-08-27 18:55:41 +04:00
|
|
|
sources = \
|
2011-06-21 19:41:57 +04:00
|
|
|
common_sm.c
|
2010-08-23 20:04:13 +04:00
|
|
|
|
2009-10-02 21:13:56 +04:00
|
|
|
# Help file
|
|
|
|
|
2014-07-31 08:41:04 +04:00
|
|
|
dist_opaldata_DATA = help-mpi-common-sm.txt
|
2009-10-02 21:13:56 +04:00
|
|
|
|
2004-08-27 18:55:41 +04:00
|
|
|
# As per above, we'll either have an installable or noinst result.
|
|
|
|
# The installable one should follow the same MCA prefix naming rules
|
|
|
|
# (i.e., libmca_<type>_<name>.la). The noinst one can be named
|
|
|
|
# whatever it wants, although libmca_<type>_<name>_noinst.la is
|
|
|
|
# recommended.
|
|
|
|
|
|
|
|
# To simplify components that link to this library, we will *always*
|
|
|
|
# have an output libtool library named libmca_<type>_<name>.la -- even
|
|
|
|
# for case 2) described above (i.e., so there's no conditional logic
|
|
|
|
# necessary in component Makefile.am's that link to this library).
|
|
|
|
# Hence, if we're creating a noinst version of this library (i.e.,
|
|
|
|
# case 2), we sym link it to the libmca_<type>_<name>.la name
|
|
|
|
# (libtool will do the Right Things under the covers). See the
|
|
|
|
# all-local and clean-local rules, below, for how this is effected.
|
|
|
|
|
|
|
|
lib_LTLIBRARIES =
|
|
|
|
noinst_LTLIBRARIES =
|
configury: new OPAL_SET_LIB_PREFIX/ORTE_SET_LIB_PREFIX macros
These two macros set the prefix for the OPAL and ORTE libraries,
respectively. Specifically, the OPAL library will be named
libPREFIXopen-pal.la and the ORTE library will be named
libPREFIXopen-rte.la.
These macros must be called, even if the prefix argument is empty.
The intent is that Open MPI will call these macros with an empty
prefix, but other projects (such as ORCM) will call these macros with
a non-empty prefix. For example, ORCM libraries can be named
liborcm-open-pal.la and liborcm-open-rte.la.
This scheme is necessary to allow running Open MPI applications under
systems that use their own versions of ORTE and OPAL. For example,
when running MPI applications under ORTE, if the ORTE and OPAL
libraries between OMPI and ORCM are not identical (which, because they
are released at different times, are likely to be different), we need
to ensure that the OMPI applications link against their ORTE and OPAL
libraries, but the ORCM executables link against their ORTE and OPAL
libraries.
2014-10-22 16:49:58 +04:00
|
|
|
comp_inst = lib@OPAL_LIB_PREFIX@mca_common_sm.la
|
|
|
|
comp_noinst = lib@OPAL_LIB_PREFIX@mca_common_sm_noinst.la
|
2004-08-27 18:55:41 +04:00
|
|
|
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
if MCA_BUILD_opal_common_sm_DSO
|
2004-08-27 18:55:41 +04:00
|
|
|
lib_LTLIBRARIES += $(comp_inst)
|
|
|
|
else
|
|
|
|
noinst_LTLIBRARIES += $(comp_noinst)
|
|
|
|
endif
|
|
|
|
|
configury: new OPAL_SET_LIB_PREFIX/ORTE_SET_LIB_PREFIX macros
These two macros set the prefix for the OPAL and ORTE libraries,
respectively. Specifically, the OPAL library will be named
libPREFIXopen-pal.la and the ORTE library will be named
libPREFIXopen-rte.la.
These macros must be called, even if the prefix argument is empty.
The intent is that Open MPI will call these macros with an empty
prefix, but other projects (such as ORCM) will call these macros with
a non-empty prefix. For example, ORCM libraries can be named
liborcm-open-pal.la and liborcm-open-rte.la.
This scheme is necessary to allow running Open MPI applications under
systems that use their own versions of ORTE and OPAL. For example,
when running MPI applications under ORTE, if the ORTE and OPAL
libraries between OMPI and ORCM are not identical (which, because they
are released at different times, are likely to be different), we need
to ensure that the OMPI applications link against their ORTE and OPAL
libraries, but the ORCM executables link against their ORTE and OPAL
libraries.
2014-10-22 16:49:58 +04:00
|
|
|
lib@OPAL_LIB_PREFIX@mca_common_sm_la_SOURCES = \
|
|
|
|
$(headers) $(sources)
|
|
|
|
lib@OPAL_LIB_PREFIX@mca_common_sm_la_LDFLAGS = \
|
|
|
|
-version-info $(libmca_common_sm_so_version)
|
|
|
|
lib@OPAL_LIB_PREFIX@mca_common_sm_noinst_la_SOURCES = \
|
|
|
|
$(lib@OPAL_LIB_PREFIX@mca_common_sm_la_SOURCES)
|
2004-08-27 18:55:41 +04:00
|
|
|
|
2004-08-06 23:35:57 +04:00
|
|
|
# Conditionally install the header files
|
|
|
|
|
|
|
|
if WANT_INSTALL_HEADERS
|
George did the work and deserves all the credit for it. Ralph did the merge, and deserves whatever blame results from errors in it :-)
WHAT: Open our low-level communication infrastructure by moving all necessary components (btl/rcache/allocator/mpool) down in OPAL
All the components required for inter-process communications are currently deeply integrated in the OMPI layer. Several groups/institutions have express interest in having a more generic communication infrastructure, without all the OMPI layer dependencies. This communication layer should be made available at a different software level, available to all layers in the Open MPI software stack. As an example, our ORTE layer could replace the current OOB and instead use the BTL directly, gaining access to more reactive network interfaces than TCP. Similarly, external software libraries could take advantage of our highly optimized AM (active message) communication layer for their own purpose. UTK with support from Sandia, developped a version of Open MPI where the entire communication infrastucture has been moved down to OPAL (btl/rcache/allocator/mpool). Most of the moved components have been updated to match the new schema, with few exceptions (mainly BTLs where I have no way of compiling/testing them). Thus, the completion of this RFC is tied to being able to completing this move for all BTLs. For this we need help from the rest of the Open MPI community, especially those supporting some of the BTLs. A non-exhaustive list of BTLs that qualify here is: mx, portals4, scif, udapl, ugni, usnic.
This commit was SVN r32317.
2014-07-26 04:47:28 +04:00
|
|
|
opaldir = $(opalincludedir)/$(subdir)
|
|
|
|
opal_HEADERS = $(headers)
|
2004-08-06 23:35:57 +04:00
|
|
|
endif
|
2004-08-27 18:55:41 +04:00
|
|
|
|
|
|
|
# These two rules will sym link the "noinst" libtool library filename
|
|
|
|
# to the installable libtool library filename in the case where we are
|
|
|
|
# compiling this component statically (case 2), described above).
|
|
|
|
|
2014-03-28 22:24:32 +04:00
|
|
|
# See Makefile.ompi-rules for an explanation of the "V" macros, below
|
|
|
|
V=0
|
|
|
|
OMPI_V_LN_SCOMP = $(ompi__v_LN_SCOMP_$V)
|
|
|
|
ompi__v_LN_SCOMP_ = $(ompi__v_LN_SCOMP_$AM_DEFAULT_VERBOSITY)
|
|
|
|
ompi__v_LN_SCOMP_0 = @echo " LN_S " `basename $(comp_inst)`;
|
|
|
|
|
2004-08-27 18:55:41 +04:00
|
|
|
all-local:
|
2014-03-28 22:24:32 +04:00
|
|
|
$(OMPI_V_LN_SCOMP) if test -z "$(lib_LTLIBRARIES)"; then \
|
2004-08-27 18:55:41 +04:00
|
|
|
rm -f "$(comp_inst)"; \
|
|
|
|
$(LN_S) "$(comp_noinst)" "$(comp_inst)"; \
|
|
|
|
fi
|
|
|
|
|
|
|
|
clean-local:
|
|
|
|
if test -z "$(lib_LTLIBRARIES)"; then \
|
|
|
|
rm -f "$(comp_inst)"; \
|
|
|
|
fi
|