Hi George,
In the code I'm working on I actually have concurrent MPI_Waitany calls
on the same set of requests. Oops. All clear now.
Cheers,
Pedro
> I checked the wait_any code, and I can only see one possible execution
> path to return MPI_UNDEFINED. All requests have to be marked as
> inacti
I checked the wait_any code, and I can only see one possible execution path to
return MPI_UNDEFINED. All requests have to be marked as inactive, which only
happens after the OMPI request completion function is called.
This lead to the following question. Are your threads waiting on common
reque
Hi again,
I have a follow-up question. I have been using MPI_Init_thread and
MPI_Isend/MPI_Irecv/MPI_Waitany for a while now and have stubled over
what may be a but in MPI_Waitany...
Within a parallel region of the code (in this case I am using OpenMP),
calls to MPI_Isend and MPI_Irecv work find
Sorry for the delay -- I just replied on the users list. I think you need to
use MPI_INIT_THREAD with MPI_THREAD_MULTIPLE. See if that helps.
On Oct 26, 2011, at 7:19 AM, Pedro Gonnet wrote:
>
> Hi all,
>
> I'm forwarding this message from the "users" mailing list as it wasn't
> getting any
Hi all,
I'm forwarding this message from the "users" mailing list as it wasn't
getting any attention there and I believe this is a bona-fide bug.
The issue is that if an MPI node has two threads, one exchanging data
with other nodes through the non-blocking routines, the other exchanging
data wi
