LAM/MPI logo

LAM/MPI General User's Mailing List Archives

  |   Home   |   Download   |   Documentation   |   FAQ   |   all just in this list

From: Richard Drake (rrdrake_at_[hidden])
Date: 2003-09-27 12:49:08


Jeff,

right .. 7.0

Following is the result of laminfo. I did find and use GM with configure: --with-gm=/usr/gm-1.5.2.1_Linux-2.4.18-4smp

Does this mean that by default, MPI programs will use the native Myrinet interfaces (when, say, using straight "lamboot" on a PBS scheduled process)? Or does one need to do something special to get the native Myrinet to be used?

-rich

           LAM/MPI: 7.0
            Prefix: /data/rrdrake/lam
      Architecture: i686-pc-linux-gnu
     Configured by: rrdrake
     Configured on: Fri Sep 26 19:05:41 MDT 2003
    Configure host: master.v8.sandia.gov
        C bindings: yes
      C++ bindings: yes
  Fortran bindings: yes
       C profiling: yes
     C++ profiling: yes
 Fortran profiling: yes
     ROMIO support: yes
      IMPI support: no
     Debug support: no
      Purify clean: no
          SSI boot: globus (Module v0.5)
          SSI boot: rsh (Module v1.0)
          SSI boot: tm (Module v1.0)
          SSI coll: lam_basic (Module v7.0)
          SSI coll: smp (Module v1.0)
           SSI rpi: crtcp (Module v1.0)
           SSI rpi: gm (Module v1.0)
           SSI rpi: lamd (Module v7.0)
           SSI rpi: sysv (Module v7.0)
           SSI rpi: tcp (Module v7.0)
           SSI rpi: usysv (Module v7.0)

Jeff Squyres wrote:
>
> On Sat, 27 Sep 2003, Richard Drake wrote:
>
> > i just downloaded and installed 6.7.0 on a linux cluster using PBS and
>
> I think you mean 7.0. :-)
>
> > using GM. i like the ability of lamboot to recognize the nodes
> > available by PBS so that a boot schema file is not needed, nice!
>
> Woo hoo!
>
> > however, i am concerned that lamboot is not using the Myrinet comm
> > fabric, but rather the ethernet.
> >
> > with a boot schema, one puts "node07-myri0" instead of just "node07" to
> > trigger the Myrinet fabric.
>
> Is there a reason you're using the IP layer over Myrinet instead of native
> Myrinet? The IP layer over Myrinet adds a little more latency and reduces
> available bandwidth as compared to native Myrinet.
>
> Specifically -- if you lamboot across either IP layer (ethernet or IP
> Myrinet) and then use the "gm" RPI module, you'll be using the native
> Myrinet interface (which obviously doesn't require any IP addresses).
>
> You can check to see if you compiled in support for native Myrinet by
> running "laminfo" and see if you see the gm RPI module lised. If it's
> not, double check your ./configure settings from when you installed LAM.
> Ensure to specify --with-gm=/path/to/gm/installation. See the Install
> Guide, section 5.2.4.
>
> Note that 7.0.1 is due out "shortly", and will contain support for both gm
> 1.6.x and 2.0.x.
>
> --
> {+} Jeff Squyres
> {+} jsquyres_at_[hidden]
> {+} http://www.lam-mpi.org/
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/