On Oct 19, 2011, at 6:41 PM, George Bosilca wrote:
> A careful reading of the committed patch, would have pointed out that none of
> the concerns raised so far were true, the "old-way" behavior of the OMPI code
> was preserved.
Then perhaps you could have added some comments to explain the not-
Since people may not be fully familiar, and because things have evolved, I
thought it might help to provide a brief explanation of the ranks we assign to
processes in OMPI.
Each process has four "ranks" assigned to it at launch:
1. vpid - equivalent to its MPI rank within the job. You can acces
For those wishing to use the new locality functionality, here is a little
(hopefully clearer) info on how to do it. A few clarifications first may help:
1. the locality is defined by the precise cpu set upon which a process is
bound. If not bound, this obviously includes all the available cpus o
In MTT testing, we check OMPI version number to decide whether to test
MPI 2.2 datatypes.
Specifically, in intel_tests/src/mpitest_def.h:
#define MPITEST_2_2_datatype 0
#if defined(OPEN_MPI)
#if (OMPI_MAJOR_VERSION > 1) || (OMPI_MAJOR_VERSION == 1 &&
OMPI_MINOR_VERSION >= 7)
#unde
regenerating now...
On Oct 20, 2011, at 7:14 PM, MPI Team wrote:
>
> ERROR: Command returned a non-zero exist status (trunk):
> make distcheck
>
> Start time: Thu Oct 20 21:00:02 EDT 2011
> End time: Thu Oct 20 21:14:13 EDT 2011
>
> =
