What's the story about calling MPI_Finalize without first calling
MPI_Buffer_detach?
If I do an MPI_Bsend followed by MPI_Finalize, the corresponding
MPI_Recv takes forever. In contrast, if I insert an MPI_Buffer_detach,
then performance is reasonable. I can imagine the explanation. I
susp
The proper practice based on the MPI Standard will be to call the
detach function before finalize. From a pure OMPI perspective, we do
the same thing in both cases, i.e. we wait until all pending
communications on the buffer are completed to detach it. I think dhe
difference in performance
How did you configure OMPI?
What launch mechanism are you using - ssh?
On Nov 17, 2009, at 9:01 AM, Sylvain Jeaugey wrote:
> I don't think so, and I'm not doing it explicitely at least. How do I know ?
>
> Sylvain
>
> On Tue, 17 Nov 2009, Ralph Castain wrote:
>
>> We routinely launch across t
George Bosilca wrote:
The proper practice based on the MPI Standard will be to call the
detach function before finalize.
I don't find this described anywhere in the standard. To what
chapter/verse should I point a user to convince them that detach before
finalize is the proper thing to do?
There is no such statement in the MPI Standard. In fact one of the
example use exactly this: automatic detach at MPI_Finalize (example on
page 310 on MPI 2.2). However, as the standard doesn't enforce a
specific behavior, each MPI implementation can interpret/implement it
differently. There
