1
1
openmpi/opal/mca/memchecker/configure.m4

55 строки
2.2 KiB
Plaintext
Исходник Обычный вид История

dnl -*- shell-script -*-
dnl
dnl Copyright (c) 2004-2006 High Performance Computing Center Stuttgart,
dnl University of Stuttgart. All rights reserved.
dnl Copyright (c) 2008 Cisco Systems, Inc. All rights reserved.
dnl $COPYRIGHT$
dnl
dnl Additional copyrights may follow
dnl
dnl $HEADER$
dnl
dnl we only want one :)
m4_define(MCA_opal_memchecker_CONFIGURE_MODE, STOP_AT_FIRST)
AC_DEFUN([MCA_opal_memchecker_CONFIG],[
opal_show_subsubtitle "Pre-configuring the framework memchecker"
AC_MSG_CHECKING([if --enable-memchecker was specified])
AC_ARG_ENABLE(memchecker,
AC_HELP_STRING([--enable-memchecker],
[Enable memory and buffer checks. Note that disabling will *also* add "memchecker" to the --enable-mca-no-build list (default: disabled)]))
if test "$enable_memchecker" = "yes"; then
AC_MSG_RESULT([yes])
WANT_MEMCHECKER=1
else
AC_MSG_RESULT([no (adding "memchecker" to --enable-mca-no-build list)])
WANT_MEMCHECKER=0
# Setting this environment variable causes
# MCA_COMONENT_BUILD_CHECK (in opal_mca.m4, invoked by
# MCA_CONFIGURE_FRAMEWORK, below) to rule that the component
# should not be built. It is effectively the same as adding
# "memchecker" to the --enable-mca-no-build list.
DISABLE_memchecker=1
fi
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
AC_DEFINE_UNQUOTED([OPAL_WANT_MEMCHECKER],
[$WANT_MEMCHECKER],
[if the memory and buffer checking should be enabled])
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
AM_CONDITIONAL([OPAL_WANT_MEMCHECKER],
[test "$WANT_MEMCHECKER" = "1"])
# first, compile all the components
MCA_CONFIGURE_FRAMEWORK($1, $2, 1)
AS_IF([test "$MCA_opal_memchecker_STATIC_COMPONENTS" != "" -o "$MCA_opal_memchecker_DSO_COMPONENTS" != ""],
[memchecker_base_found=1],
[memchecker_base_found=0])
AS_IF([test $WANT_MEMCHECKER -eq 1 -a $memchecker_base_found -eq 0],
[AC_MSG_WARN([Memchecker support requested, but no memchecker])
AC_MSG_WARN([components configured successfully. Did you])
AC_MSG_WARN([forget --with-valgrind?])
AC_MSG_ERROR([Cannot continue])])
])