On Tue, 13 Apr 2004, Mike Sullivan wrote:
> I am using gm 2.0.11 with lam 7.04.
>
> I start lamd with:
> lamboot -d -ssi rpi gm ../bhost.def
Note that the "gm" RPI is for MPI communications, not for lamboot.
lamboot is only for starting the run-time environment. So while it's not
[technically] wrong to say "-ssi rpi gm" to lamboot, telling lamboot which
RPI module to use is somewhat useless -- rpi modules are not used in
lamboot.
> when I run an mpi app I get:
>
> -------------------------------
> The rpi module named "gm" could not be found.
So your laminfo shows that the gm module is present. Next things to
check:
- ensure that your MPI application is compiled and linked against this
installation of LAM (that has the gm rpi module)
> What is the status of gm 2.0.x support in lam?
The gm module should figure out which version of gm is installed (1.x or
2.x) and set itself up appropriately. Long message passing has a bit
better performance under gm 2.x because Myricom added more DMA support in
that version.
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
