359464a144
--enable-mpi-ext configure switch in the top-level README file).
See Josh's excellent wiki page about OMPI extensions:
https://svn.open-mpi.org/trac/ompi/wiki/MPIExtensions
This extension exposes a new API to MPI applications:
{{{
int OMPI_Affinity_str(char ompi_bound[OMPI_AFFINITY_STRING_MAX],
char current_binding[OMPI_AFFINITY_STRING_MAX],
char exists[OMPI_AFFINITY_STRING_MAX]);
}}}
It returns 3 things. Each are a prettyprint string describing sets of
processors in terms of sockets and cores:
1. What Open MPI bound this process to. If Open MPI didn't bind this
process, the prettyprint string says so.
1. What this process is currently bound to. If the process is
unbound, the prettyprint string says so. This string is a
separate OUT parameter to detect the case where some other entity
bound the process (potentially after Open MPI bound it).
1. What processors are availabile in the system, mainly for reference.
This commit was SVN r23018.
18 строки
565 B
Plaintext
18 строки
565 B
Plaintext
Copyright (c) 2010 Cisco Systems, Inc. All rights reserved.
|
|
|
|
Jeff Squyres
|
|
19 April 2010
|
|
|
|
This extension provides a single new function, OMPI_Affinity_str(),
|
|
that provides 3 prettyprint strings as output:
|
|
|
|
ompi_bound: describes what sockets/cores Open MPI bound this process
|
|
to (or indicates that Open MPI did not bind this process).
|
|
|
|
currently_bound: describes what sockets/cores this process is
|
|
currently bound to (or indicates that it is unbound).
|
|
|
|
exists: describes what processors are available in the current host.
|
|
|
|
See OMPI_Affinity_str(3) for more details.
|