Looking at this a little closer on the v1.2 branch, it does look like
it could be a bug.
The child definitely does not return from INTERCOMM_MERGE until the
parent enters MPI_RECV. So I put in a bogus MPI_TEST call before the
parent calls MPI_RECV, and that also causes the child the return
On Jul 28, 2008, at 4:56 PM, Aurélien Bouteiller wrote:
Having different values is fine for high parameter.
I think the problem comes from using NULL, NULL instead of &argc,
&argv as parameters for MPI_Init.
Calling MPI_INIT with NULL, NULL is legal; we don't actually do
anything with tho
Having different values is fine for high parameter.
I think the problem comes from using NULL, NULL instead of &argc,
&argv as parameters for MPI_Init. This toy application works for me on
trunk. If you still experience troubles on 1.2, please let us know.
**
intercomm_
Check.
Parent has high=0
Children have high=1
Jeff Squyres wrote:
Ok, good.
One thing to check is that you have put different values for the
"high" value between the parent group and the children group.
On Jul 28, 2008, at 3:42 PM, Mark Borgerding wrote:
I should've been clearer. I hav
Ok, good.
One thing to check is that you have put different values for the
"high" value between the parent group and the children group.
On Jul 28, 2008, at 3:42 PM, Mark Borgerding wrote:
I should've been clearer. I have observed the same behavior under
both those versions.
I was not u
I should've been clearer. I have observed the same behavior under both
those versions.
I was not using the two version in the same cluster.
-- Mark
Jeff Squyres wrote:
Are you mixing both v1.2.4 and v1.2.5 in a single MPI job? That may
have unintended side-effects -- we unfortunately do not
Are you mixing both v1.2.4 and v1.2.5 in a single MPI job? That may
have unintended side-effects -- we unfortunately do not guarantee
binary compatibility between any of our releases.
On Jul 28, 2008, at 10:16 AM, Mark Borgerding wrote:
I am using version 1.2.4 (Fedora 9) and 1.2.5 ( Cent
I am using version 1.2.4 (Fedora 9) and 1.2.5 ( CentOS 5.2 )
A little clarification:
The children do not actually wake up when the parent *sends* data to
them, but only after the parent tries to receive data from the merged
intercomm.
Here is the timeline:
...
parent call to MPI_Comm_spawn
Ok, I'll check to see what happens. Which version of Open MPI are you
using ?
Aurelien
Le 27 juil. 08 à 23:13, Mark Borgerding a écrit :
I got something working, but I'm not 100% sure why.
The children woke up and returned from their calls to
MPI_Intercomm_merge only after
the parent used
I got something working, but I'm not 100% sure why.
The children woke up and returned from their calls to
MPI_Intercomm_merge only after
the parent used the intercomm to send some data to the children via
MPI_Send.
Mark Borgerding wrote:
Perhaps I am doing something wrong. The childrens' c
Perhaps I am doing something wrong. The childrens' calls to
MPI_Intercomm_merge never return.
Here's the chronology (with 2 children):
parent calls MPI_Init
parent calls MPI_Comm_spawn
child calls MPI_Init
child calls MPI_Init
parent call to MPI_Comm_spawn returns
(long pause inserted)
parent c
MPI_Intercomm_merge is what you are looking for.
Aurelien
Le 26 juil. 08 à 13:23, Mark Borgerding a écrit :
Okay, so I've gotten a little bit closer.
I'm using MPI_Comm_spawn to start several children processes. The
problem is that the children are in their own group, separate from
the pa
Okay, so I've gotten a little bit closer.
I'm using MPI_Comm_spawn to start several children processes. The
problem is that the children are in their own group, separate from the
parent (just the like the documentation says). I want to merge the
children's group with the parent group so I ca
I am writing a code module that plugs into a larger application
framework. That framework loads my code module as a shared object.
So I do not control how the first process gets started, but I still want
it to be able to start and participate in an MPI group.
Here's roughly what I want to happ
14 matches
Mail list logo
