552c9ca5a0
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.
35 строки
1.1 KiB
Plaintext
35 строки
1.1 KiB
Plaintext
# -*- text -*-
|
|
#
|
|
# Copyright (c) 2009-2010 Cisco Systems, Inc. All rights reserved.
|
|
# Copyright (c) 2010-2012 Los Alamos National Security, LLC.
|
|
# All rights reserved.
|
|
#
|
|
# $COPYRIGHT$
|
|
#
|
|
# Additional copyrights may follow
|
|
#
|
|
# $HEADER$
|
|
#
|
|
# This is the US/English help file for Open MPI's common shmem support.
|
|
#
|
|
[mmap too small]
|
|
Open MPI requested a shared memory segment that was too small to do
|
|
anything useful. This is likely an error in Open MPI itself. If you
|
|
see this error, you should see if there is an update available for
|
|
Open MPI, and if not, contact the Open MPI developers.
|
|
|
|
Local host: %s
|
|
Requested size: %ul
|
|
Control seg size: %ul
|
|
Data seg aligment: %ul
|
|
#
|
|
[unexpected message id]
|
|
Open MPI received an unexpected message ID during common sm initialization.
|
|
This is likely an error in Open MPI itself. If you see this error, you should
|
|
see if there is an update available for Open MPI that addresses this issue, and
|
|
if not, contact the Open MPI developers.
|
|
|
|
Local Host: %s
|
|
Expected Message ID: %s
|
|
Message ID Received: %s
|