Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI users] Unexpected behavior: MPI_Comm_accept, MPI_Comm_connect, and MPI_THREAD_MULTIPLE
From: Ralph Castain (rhc_at_[hidden])
Date: 2013-05-14 16:02:25

On May 14, 2013, at 12:56 PM, Damien Kick <dkick_at_[hidden]> wrote:

> On May 14, 2013, at 1:46 PM, Ralph Castain <rhc_at_[hidden]>
> 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 concurrent clients with Open MPI 1.6.4 is to use multiple processes to handle each client connection, yes?

Or introduce your own thread protection around the comm_accept call

> ________________________________
> This e-mail and any attachments are confidential. If it is not intended for you, please notify the sender, and please erase and ignore the contents.
> _______________________________________________
> users mailing list
> users_at_[hidden]