This is correct -- the MPI_ERROR field should be filled in by the MTL upon
completion of the request (or when it knows what to stick in there). The
CM PML should generally not fill in that field.
Brian
On Wed, 31 Oct 2007, Jeff Squyres wrote:
Again, I'm not a CM guy :-), but in general, I w
Again, I'm not a CM guy :-), but in general, I would think: yes, you
set MPI_ERROR when it is appropriate. I.e., when you know that the
request has been successful or it has failed.
On Oct 31, 2007, at 9:18 AM, Sajjad Tabib wrote:
Hi Jeff,
Now that you mention it, I believe you are righ
Hi Jeff,
Now that you mention it, I believe you are right. In fact, I did not know
that I needed to set the req_status.MPI_ERROR in my MTL. I looked at the
mx mtl and realized that req_status.MPI_ERROR is getting set in their
progress function. So, in general, when do you set the
req_status.MP
On Tue, 30 Oct 2007, Bogdan Costescu wrote:
Bad timing... I don't have access to the files at the moment, I'll
write back shortly (which probably means tomorrow ;-)).
Here they are:
http://spider.iwr.uni-heidelberg.de/~bogdan/openmpi/
Due to their size, I decided to put them up on a web serv
I haven't done any work in the cm pml so I can't definitively answer
your question, but wouldn't you set req_status.MPI_ERROR in your MTL
depending on the result of the request?
On Oct 29, 2007, at 9:20 AM, Sajjad Tabib wrote:
Hi,
I was issuing an MPI_Bcast in a sample program and was hi
