Re: [OMPI users] Unexpected behavior: MPI_Comm_accept, MPI_Comm_connect, and MPI_THREAD_MULTIPLE

On May 14, 2013, at 3:02 PM, Ralph Castain wrote: > > On May 14, 2013, at 12:56 PM, Damien Kick wrote: > >> >> On May 14, 2013, at 1:46 PM, Ralph Castain >> wrote: >> >>> Problem is that comm_accept isn't thread safe in 1.6 series -

Re: [OMPI users] Unexpected behavior: MPI_Comm_accept, MPI_Comm_connect, and MPI_THREAD_MULTIPLE

On May 14, 2013, at 1:46 PM, Ralph Castain wrote: > Problem is that comm_accept isn't thread safe in 1.6 series - we have a devel > branch that might solve it, but is still under evaluation So then probably the only way to implement an MPI server which handles multiple

Re: [OMPI users] Unexpected behavior: MPI_Comm_accept, MPI_Comm_connect, and MPI_THREAD_MULTIPLE

Problem is that comm_accept isn't thread safe in 1.6 series - we have a devel branch that might solve it, but is still under evaluation On May 14, 2013, at 11:15 AM, Damien Kick wrote: > I'm been playing with come code to try and become familiar with > MPI_Comm_accept and

[OMPI users] Unexpected behavior: MPI_Comm_accept, MPI_Comm_connect, and MPI_THREAD_MULTIPLE

I'm been playing with come code to try and become familiar with MPI_Comm_accept and MPI_Comm_connect to implement an MPI client/server. The code that I have simply sends a single MPI_INT, the client process pid, to the server and then disconnects. The code that I have works for a few test runs