- Is the Intel® MPI Library thread safe?
- Is the Intel MPI Library fault-tolerant?
- Does the Intel MPI Library support parallel I/O calls?
- Does the Intel MPI Library support one-sided communication?
- Does the Intel MPI Library support heterogeneous clusters?
- Does the Intel MPI Library support 32-bit applications on 64-bit operating systems?
- Can the Intel MPI Library handle a mixed 32/64-bit job?
- Does the Intel MPI Library support the same user running MPD daemons simultaneously?
- Is there a Microsoft Windows* version of the Intel MPI Library?
- How do I check a process pinning table?
- How do I verify the Intel MPI Library environment variables in effect?
Is the Intel® MPI Library thread safe?
MPI_THREAD_MULTIPLE since version 3.0. Several threads can make the Intel MPI library calls simultaneously. Use the compiler driver -mt_mpi option to link the thread safe version of the Intel MPI Library. Use the thread safe libraries if you request the thread support at the following levels:
The previous versions of the Intel® MPI provide only Is the Intel MPI Library fault-tolerant? Does the Intel MPI Library support parallel I/O calls? Does the Intel MPI Library support one-sided communication? Does the Intel MPI Library support heterogeneous clusters? Does the Intel MPI Library support 32-bit applications on 64-bit operating systems? Can the Intel MPI Library handle a mixed 32/64-bit job? Does the Intel MPI Library support the same user running MPD daemons simultaneously? How do I check the process pinning table?MPI_THREAD_FUNNELED,MPI_THREAD_SERIALIZED, orMPI_THREAD_MULTIPLE.MPI_THREAD_NONE and MPI_THREAD_FUNNELED levels in terms of the MPI-2 standard.
No. The only fault tolerant feature implemented at the moment is the ability to fall back upon the default sock device in case the Intel MPI Library device selected by the user at runtime cannot be initialized for some reason.
Set the I_MPI_FALLBACK_DEVICE environment variable to "disable" to prevent fallback. In this case, if an attempt to initialize the specified fabric fails, the library terminates the MPI job.
Note: This is true for RDSSM or RDMA modes only.
Yes. The parallel file I/O part of the MPI-2 standard is fully implemented by the Intel MPI Library. File systems currently supported include the Unix File System (UFS) and the Network File System (NFS).
Yes. The Intel MPI Library supports both active target and passive target one-sided communication. The only exception is the passive target one-sided communication in case the target process does not call any MPI functions.
No. The Intel MPI Library does not support clusters with nodes of different architecture or operating environment.
Yes. The Intel MPI Library supports 32-bit apps on 64-bit operating systems on Intel® 64 platforms.
No. The Intel MPI Library does not support heterogeneous configurations. The entire job must be IA32, Intel® 64, or Itanium® based.
Yes. The Intel MPI Library supports simultaneous MPD rings. Use the mpirun job launcher. It will create an independent MPD ring, start the requested MPI job over it, and clean up the ring when the job terminates. You can launch several MPI jobs simultaneously. It is also possible to use the I_MPI_JOB_CONTEXT environment variable. Set this variable to an unique value before each MPD ring starts.Example 1:
login on clustermpirun -np [args]
login on clustermpirun -np [args]
Example 2:
login on clusterexport I_MPI_JOB_CONTEXT=ext1
mpdboot -n numnodes
login on clusterexport I_MPI_JOB_CONTEXT=ext2
mpdboot -n numnodes
Is there a Microsoft* Windows* version of the Intel MPI Library?
Yes. There is the Intel MPI Library for Windows (and Linux). Go to http://www.intel.com/go/mpi for more details.I_MPI_DEBUG environment variable to "4". The Intel MPI Library will report process pinning information.
For example:
mpiexec -np -env I_MPI_DEBUG 4 $executable
How do I verify the Intel MPI Library variables in effect?
Set the I_MPI_DEBUG environment variable to "5". The Intel MPI Library will report effective Intel MPI Library environment variables.
For example:mpiexec -np -env I_MPI_DEBUG 5 $executable.
Operating System:
SUSE* Linux Enterprise Server 10, Red Hat* Enterprise Linux 5.0, SUSE* Linux Enterprise Server 9, Red Hat* Enterprise Linux 4.0
