Hi,
s anwar wrote:
> Please see attached source file.
>
> According to my understanding of MPI_Comm_spawn(), the intercommunicator
> returned is the same as it is returned by MPI_Comm_get_parent() in the
> spawned processes. I am assuming that there is one intercommunicator
> which contains all
Dear Brian,
Thanks for the help
Brian Barrett wrote:
> > The arguments you want would look like:
> >
> >mpirun -np X -mca btl gm,sm,self -mca btl_base_verbose 1 -mca
> > btl_gm_debug 1
Aha. I think I had misunderstood the syntax slightly, which explains why
I previously saw no debugging
On Tue, Jul 11, 2006 at 12:14:51PM -0400, Abhishek Agarwal wrote:
> Hello,
>
> Is there a way of providing a specific port number in MPI_Info when using a
> MPI_Open_port command so that clients know which port number to connect.
The other replies have covered this pretty well but if you are
hi,
yes sorry for my first reply, my words were to rough.
a bcast for a intercomm works this way (in your words):
- your masters want to send a buffer to your slaves
- one of the masters must provide the MPI_ROOT as root in the MPI_BCAST call
- all slaves must provide the rank of this MPI_ROOT
hi,
s anwar wrote:
> Thank you for the clarification. Why is MPI_COMM_SELF not the correct
> communicator for MPI_Comm_spawn(). My application will have a single
> master only.
yes for a single master this should be the same, but never try this.
>
> Also, can I merge the intercommunicator into
Thanks.
On 7/18/06, Bert Wesarg wrote:
hi,
s anwar wrote:
> Thank you for the clarification. Why is MPI_COMM_SELF not the correct
> communicator for MPI_Comm_spawn(). My application will have a single
> master only.
yes for a single master this should be the
Okay...this isn't a performance summary or anything like that. Its
just some information on what I was able to get to work. With a
couple of suggestions from Brian Barrett about building OMPI with
static libraries (possible problem with GNU libtool support for the
Intel compiler on OS X?).