On Sat, 27 Sep 2003, Richard Drake wrote:
> if i am reading it right, it is choosing tcp. the first attachment is
> from a naked (PBS) lamboot then
> mpirun -np 4 -ssi rpi_verbose level:1000 a.out
Correct. Looks like LAM was configured with --with-rpi=tcp -- i.e., tcp
is artifically elevated to be the default (i.e., its default priority was
raised to 75). So if you don't specify anything, it'll use that TCP as a
default (sorry, didn't clarify that in my previous mail).
> and the second (from the same lamboot) is from
> mpirun -np 4 -ssi rpi gm -ssi rpi_verbose level:1000 a.out
Right -- that one is using gm.
The exact mechanism here is that when you specify an RPI on the mpirun
command line, then *only* that RPI is queried. So if it returns any valid
priority, that module will be used. That's what's happening here -- gm is
the only module checked, and therefore it has the highest priority.
> so i guess i'll have to add the switch to get GM? is there a configure
> switch i can give to make GM the default?
If you don't use --with-rpi to configure (which means that none of the
RPI's will have their priorities artifically inflated), or if you use
--with-rpi=gm (then gm will have its priority inflated) then gm should win
in the priority handshake.
Remember that every RPI has a priority that can be set either via the
mpirun command line (via -ssi) or via environment variables
(LAM_MPI_SSI_parameter_name).
All this stuff is documented is section 6.4 of the user manual, if you
care. :-)
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
