[mvapich-discuss] How do I build mvapich2 on QLOGIC IB?

[Dhabaleswar Panda]

With the latest MVAPICH2 1.4RC1, both MVAPICH and MVAPICH2 have now
support for Qlogic InfiniPath adapters at the PSM layer. You need to have
the latest PSM layer available.

For building MVAPICH 1.1 with the PSM layer, please take a look at MVAPICH
1.1 user guide at the following URL:

http://mvapich.cse.ohio-state.edu/support/mvapich_user_guide-1.1.html#x1-120004.4.3

For building MVAPICH2 1.4RC1 with the PSM layer, please take a look at
MVAPICH2 1.4 user guide at the following URL:

http://mvapich.cse.ohio-state.edu/support/user_guide_mvapich2-1.4rc1.html#x1-120004.6

You can also refer to these user guides for additional information on
running MPI applications at the PSM layer, trouble shooting, etc.

Hope this helps.

DK


On Sun, 7 Jun 2009, Divi Venkateswarlu wrote:

>   Dear all:
>
>   I am trying to install MVAPICH and MVAPICH2 on a SUN cluster with QLOGIC IB hardware.
>
>   The system has qlogic mpi compiled with gnu compilers. I have problems using this setup
>   for the chemistry package I am interested in. (This package compiles well on my in-house cluster
>   using mellanox IB/OFED/MVAPICH/INTEL comibination with pretty good scaling)
>
>   So I am interested in installing MVAPICH/MVAPICH2 with intel compilers on the new cluster I got
>   access to.
>
>   I have the following questions:
>
>   1. The machine does not have ibverbs (that I am familar with in my in-house cluster with OFED)
>
>    2. What are my options to get mvapich compiled on this Qlogic fabric?
>
>    3. I am not sure what options I choose during configure script of mvapich2 (or mvapich)
>
>   The following are some concerned files for mpi on this machine.
>
>     ldd libvapi.so
>         libibt.so.0.0 => /lib64/libibt.so.0.0 (0x000000333d200000)
>         libpublic.so.0.0 => /lib64/libpublic.so.0.0 (0x000000333d600000)
>         libpthread.so.0 => /lib64/libpthread.so.0 (0x00000032d4200000)
>         libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00000032d5e00000)
>         libm.so.6 => /lib64/libm.so.6 (0x00000032d3e00000)
>         libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00000032d5600000)
>         libc.so.6 => /lib64/libc.so.6 (0x00000032d3600000)
>         libdl.so.2 => /lib64/libdl.so.2 (0x00000032d3a00000)
>         /lib64/ld-linux-x86-64.so.2 (0x00000032d3000000)
>
>    ldd libmosal.so
>         libpthread.so.0 => /lib64/libpthread.so.0 (0x00000032d4200000)
>         libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00000032d5e00000)
>         libm.so.6 => /lib64/libm.so.6 (0x00000032d3e00000)
>         libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00000032d5600000)
>         libc.so.6 => /lib64/libc.so.6 (0x00000032d3600000)
>         /lib64/ld-linux-x86-64.so.2 (0x00000032d3000000)
>
>   ldd ./libmtl_common.so
>         libpthread.so.0 => /lib64/libpthread.so.0 (0x00000032d4200000)
>         libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00000032d5e00000)
>         libm.so.6 => /lib64/libm.so.6 (0x00000032d3e00000)
>         libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00000032d5600000)
>         libc.so.6 => /lib64/libc.so.6 (0x00000032d3600000)
>         /lib64/ld-linux-x86-64.so.2 (0x00000032d3000000)
>
>    Thanks for your input
>    Divi
>
>
>
>
>
>
>