HP-MPI User's Guide (11th Edition)

Standard-flexibility in HP-MPI
HP-MPI implementation of standard flexibility
Appendix B 281
MPI does not provide
mechanisms to specify the initial
allocation of processes to an MPI
computation and their initial
binding to physical processes.
See MPI-1.2 Section 2.6.
HP-MPI provides the mpirun -np
# utility and appfiles as well as
startup integrated with other job
schedulers and launchers. Refer to
the relevant sections in this guide.
MPI does not mandate that any
I/O service be provided, but does
suggest behavior to ensure
portability if it is provided. See
MPI-1.2 Section 2.8.
Each process in HP-MPI
applications can read and write
data to an external drive. Refer to
“External input and output” on
page 210 for details.
The value returned for MPI_HOST
gets the rank of the host process
in the group associated with
MPI_COMM_WORLD.
MPI_PROC_NULL is returned if
there is no host. MPI does not
specify what it means for a
process to be a host, nor does it
specify that a HOST exists.
HP-MPI always sets the value of
MPI_HOST to MPI_PROC_NULL.
MPI provides
MPI_GET_PROCESSOR_NAME to
return the name of the processor
on which it was called at the
moment of the call. See MPI-1.2
Section 7.1.1.
If you do not specify a host name
to use, the hostname returned is
that of gethostname. If you specify
a host name using the -h option to
mpirun, HP-MPI returns that host
name.
The current MPI definition does
not require messages to carry
data type information. Type
information might be added to
messages to allow the system to
detect mismatches. See MPI-1.2
Section 3.3.2.
The default HP-MPI library does
not carry this information due to
overload, but the HP-MPI
diagnostic library (DLIB) does. To
link with the diagnostic library,
use -ldmpi on the link line.
Table B-1 HP-MPI implementation of standard-flexible issues (Continued)
Reference in MPI standard HP-MPI’s implementation