On Tue, 22 Apr 2003, Jones, Donald E wrote:
> Does LAM MPI run over Myrinet? If so, is there anything that needs to be
> done to configure LAM to run over Myrinet? There are old posts (years
> old; from 2000/2001) along these lines in the mail archives, but nothing
> on the web site that indicates support for LAM running over Myrinet. We
> just got our first Linux cluster, so we are only just beginning to port
> codes and explore how it works. The cluster has Myrinet, so obviously we
> would like to run MPI over that as opposed to Ethernet.
LAM 7.0 includes a native GM point-to-point message passing device.
LAM has formally entered feature/code freeze for 7.0. We hope to have it
released within the next few weeks. That being said, we're doing a few
rounds of internal testing before we release some betas for public
consumption. We hope to have these public betas within a week or so.
However, if you're feeling bold, feel free to grab an anonymous CVS
checkout or a nightly snapshot tarball (http://www.lam-mpi.org/cvs/) and
give it a whirl. Documentation is lacking at the moment, but it will be
complete by 7.0 (in the meantime, see lamssi(7), lamssi_rpi(7),
lamssi_boot(7), and lamssi_coll(7)).
There's a lot of new features in 7.0 -- have a look at
http://www.lam-mpi.org/cvs/new.php relatively unsorted list of the new
stuff. The docs for 7.0 will list the major new features by the time we
get to release. Here's a quick tease:
- Myrinet (gm) support
- MagPIe-based collective algorithms for SMPs
- tm (OpenPBS / PBSPro) job control support
- bproc job control support
- ability to choose underlying RPI (message passing protocol) at run time
(vs. compile time)
- Totalview debugger support
- C++ bindings for all supported MPI functions and constants
> Assuming LAM runs over Myrinet, I have a related question. We just
> updated our version of LAM from 6.5.4 to 6.5.9 via RPM binaries. Will
> binary updates via RPM run over Myrinet, or do we need to build from
> source to enable Myrinet gm?
Because of licensing issues, we probably can't distribute an RPM with
statically linked GM code (IANAL, and I have not researched this
thoroughly, though). :-(
So you'll likely have to build LAM from source for native support of any
of the following:
- gm (Myrinet)
- tm (OpenPBS / PBSPro)
- bproc
Hopefully, that should be as simple as:
$ ./configure --prefix=/your/lam/dir --with-gm=/path/to/gm \
--with-tm=/path/to/tm --with-bproc=/path/to/bproc
[...go get some coffee...]
$ make all install
[...go get some coffee...]
:-)
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
