On Dec 17, 2010, at 2:50 PM, Suraj Prabhakaran wrote:
> Yes, with MPI_Finalize() called before an abrupt exit() it is clean but
> talking generally about releasing connections, if Process A and Process B are
> connected through MPI_Comm_connect/accept and then made to
> MPI_Comm_disconnect at a
On 12/17/2010 06:24 PM, George Bosilca wrote:
Let me try to round the edges on this one. It is not that we couldn't or wouldn't like to have a more "MPI" compliant
approach on this, but the definition of connected processes in the MPI standard is [kind of] shady. One thing is clear however,
i
On Dec 17 2010, George Bosilca wrote:
Let me try to round the edges on this one. It is not that we couldn't or
wouldn't like to have a more "MPI" compliant approach on this, but the
definition of connected processes in the MPI standard is [kind of] shady.
One thing is clear however, it is a t
Let me try to round the edges on this one. It is not that we couldn't or
wouldn't like to have a more "MPI" compliant approach on this, but the
definition of connected processes in the MPI standard is [kind of] shady. One
thing is clear however, it is a transitive relationship. If A is "connecte
No, the threads share the underlying resources (connections included). This is
required by the matching semantic of MPI, where the matching has to be done in
order per peers.
There is no paper related to this topic [unfortunately].
george.
On Dec 17, 2010, at 02:47 , 张晶 wrote:
> In the MPI_
That is the expected behavior designed into Open MPI. If any process calls
MPI_Init and then terminates without calling MPI_Finalize, we flag that as an
abnormal termination and abort the entire job.
We don't provide any option for avoiding that behavior.
On Dec 17, 2010, at 5:13 AM, Suraj Prab
On Dec 17 2010, Suraj Prabhakaran wrote:
I am observing a behavior where when the parent spawns a child and when
the child terminates abruptly (for example with exit() before
MPI_Finalize() ), the parent also terminates even after both the child
and parent have explicitly called a MPI_disconn
Hello,
I have been having some problems with connect and disconnect between two
processes. The processes seem to be indefinitely blocking at
Connect/Accept stage or at Disconnect stage. For example
Process A
{
MPI_Open_port(...);
MPI_Publish_name(...);
MPI_Comm_accept(... &b_comm)
Hello,
I am observing a behavior where when the parent spawns a child and when
the child terminates abruptly (for example with exit() before
MPI_Finalize() ), the parent also terminates even after both the child
and parent have explicitly called a MPI_disconnect. This turns out to be
a disadv
In the MPI_THREAD_MULTIPLE mode ,every thread can use MPI_Send(),
MPI_Recv() simulately. I wonder the connection architectures behind the
implement。Does every thread have its own specific socket storage？Or all the
thread share the same socket when they connect to the same rank process and
use some
10 matches
Mail list logo
