Fwd: [Bug 622] Trouble with autoconf + LA-MPI

From: Dan Bonachea (bonachea_at_cs_dot_berkeley_dot_edu)
Date: Thu May 27 2004 - 16:10:38 PDT

  • Next message: P Mehta: "Shared structures"
    Ben - If you have Mellanox Infiniband hardware, you really should be using 
    GASNet's vapi-conduit, which was written to natively support this hardware and 
    gives *much* better performance than mpi-conduit on Infiniband.
    mpi-conduit is a "portable" option for networks where we lack native support 
    and rarely gives the best performance the hardware can offer. It's definitely 
    worth it to set up vapi-conduit instead - mpi-conduit is not recommended for 
    high performance on Infiniband. Be sure to use the version in the stable 
    snapshot, which I believe includes some important vapi-conduit fixes.
    
    However, note that vapi-conduit currently uses MPI for job bootstrapping, so 
    you'll still need to get GASNet's configure to recognize *some* functional MPI 
    installation (although it need not be a fast one - MPICH-Ethernet would be 
    sufficient).
    
    Dan
    
    >Date: Thu, 27 May 2004 12:05:14 -0700
    >From: bugzilla-daemon_at_mantis_dot_lbl_dot_gov
    >Subject: [Bug 622] Trouble with autoconf + LA-MPI
    >Sender: owner-upc-devel_at_lbl_dot_gov
    >To: upc-devel_at_lbl_dot_gov
    >
    >http://mantis.lbl.gov/bugzilla/show_bug.cgi?id=622
    >
    >
    >
    >
    >---- Additional Comments From PHHargrove_at_lbl_dot_gov  2004-05-27 12:05 ----
    >Ben,
    >   I've build lampi-1.5.1 on my InfiniBand systems and can confirm that 
    > building
    >any MPI progs with the MPI_LIBS you specified will fail - thus our configure
    >script fails.
    >
    >   If you have build libmpi.so and don't object to having UPC programs
    >dynamically linked to lampi, then try MPI_LIBS='-L/usr/local/lampi/lib 
    >-lmpi'.
    >This let me build regular MPI programs, and configure Berkeley UPC (I've not 
    >yet
    >tried to build it).
    >
    >   If you must have a UPC program statically linked with lampi, then you need 
    > to
    >add libraries dependencies to MPI_LIBS.  You can find the dependencies from 
    >the
    >shared library as follows:
    >objdump -x /usr/local/lampi/lib/libmpi.so  | grep NEEDED
    >   NEEDED      libpthread.so.0
    >   NEEDED      libutil.so.1
    >   NEEDED      libgm.so.0
    >   NEEDED      libstdc++.so.5
    >   NEEDED      libm.so.6
    >   NEEDED      libgcc_s.so.1
    >   NEEDED      libc.so.6
    >You should run this on your own libmpi.so, rather than using the list above.
    >
    >
    >
    >------- You are receiving this mail because: -------
    >You are the QA contact for the bug, or are watching the QA contact.
    

  • Next message: P Mehta: "Shared structures"