Hi,
Sorry for the late reply.
If you want to expand the boot universe, lamgrow (more information can be
found on the manpage) can be used. Unfortunately lamgrow in not supported
on globus.
MPI_Comm_spawn is supported on globus and is used to expand MPI universe.
This means that you can do
lamboot on n0, n1, n2
mpirun n0,n1
MPI_Comm_spawn to start a process on n2 (note that the node must exist in
the machine file, used during lamboot)
Look at the examples in lamtests/lam/dynamic directory to see how MPI_Info
argument can be used for specifying how and where to start the process.
Hope this helps
Amey S. Dharurkar
----------------------------------------------------------
Graduate Student, Indiana University
Ph. O:(812)855-3609, H:(812)331-8203
On Tue, 10 Feb 2004 sbandham_at_[hidden] wrote:
> Hi,
> I am using LAM/MPI on top of globus. I am using globus to access remote
> resources and then spawing processes using MPI_Comm_spawn.
> How do I schedule these newly created processes onto the remote resources?
> Is the machines file in LAM/MPI static or dynamic - by dynamic I mean that can I
> change it after lamboot is done and notify lamboot to consider the new
> environment
>
> thanks
> Siva
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
|
