I am fine with the decision to make it the chapter committee responsibility. I suppose that means I need to draft text for the generalized requests? On Sat, 11 Feb 2012, William Gropp wrote:

It looks like this is a result of adding new request types without revisiting the original text. Under generalized requests, there is text that seems to imply that the request is set to MPI_REQUEST_NULL on completion, but it isn't explicit and should be.

This is a chapter committee correction.

Bill

On Feb 10, 2012, at 6:04 PM, Fab Tillier wrote:

Hi Folks,

Looking at the text for MPI_WAIT (page 54, line 15) and MPI_TEST (page 55, line 7), it seems to imply that the request handle is only set to MPI_REQUEST_NULL for non-blocking send and receive requests. Are generalized, I/O, and NBC requests not completed the same way? Are users required to free such requests explicitly after they complete using MPI_REQUEST_FREE?

I would have expected that all request handles except those to persistent requests are set to MPI_REQUEST_NULL, and persistent request just rather marked inactive. If that is indeed the intent, shouldn't we update the text to reflect this? Is this a ticket-0 level change?

Thanks, -Fab

_______________________________________________ mpi-forum mailing list [email protected]<mailto:[email protected]> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum

William Gropp Director, Parallel Computing Institute Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign