[mpiwg-tools] Tools WG webex tomorrow!
Schulz, Martin
schulz6 at llnl.gov
Mon Aug 26 18:23:28 CDT 2013
On Aug 27, 2013, at 1:09 AM, Kathryn Mohror <kathryn at llnl.gov<mailto:kathryn at llnl.gov>>
wrote:
Also for PVAR start, what if there are no handles associated with a session and MPI_T_PVAR_ALL_HANDLES is used? Do we return SUCCESS or ERR_PVAR_NO_STARTSTOP?
Hm. I think this is a separate ticket, yes? And I would think returning the error code would be more helpful than success. However, I can see the other side too, that success makes sense, since nothing erroneous actually happened.
Here is what the text says:
If the constant MPI_T_PVAR_ALL_HANDLES is passed in handle, the MPI implementation attempts to start all variables within the session identified by the parameter session for which handles have been allocated.
For me this reads as returning SUCCESS since all variables, which had handles allocated, have been reset. Granted, we could be more explicit.
(the same applies to stop and reset as well)
I am now on the SUCCESS side of the fence. Does it need to be clarified as an errata? I would suggest (from 3.0 clean doc):
page 580, line 41:
In this case, the routine returns MPI_SUCCESS if all variables are started successfully, otherwise MPI_T_ERR_PVAR_NO_STARTSTOP is returned. MPI_SUCCESS is also returned if no handles are valid for session and MPI_T_PVAR_ALL_HANDLES is passed in handle.
Hmm - I fear we would have to be even more explicit: MPI_SUCCESS is also returned if MPI_T_PVAR_ALL_HANDLES is passed in handles and if no handles are valid for session or all valid handles represent continuous (read only for reset) variables.
Martin
Same for 581, line 13 and page 582, line 25.
Martin
and 387
Looks good. :-)
due to lack of time (I blame Fortran!)
Long live Fortran 2028!
:-)
Kathryn
--
Jeff Squyres
jsquyres at cisco.com<mailto:jsquyres at cisco.com>
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
_______________________________________________
mpiwg-tools mailing list
mpiwg-tools at lists.mpi-forum.org<mailto:mpiwg-tools at lists.mpi-forum.org>
http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools
______________________________________________________________
Kathryn Mohror, kathryn at llnl.gov<mailto:kathryn at llnl.gov>, http://people.llnl.gov/mohror1
CASC @ Lawrence Livermore National Laboratory, Livermore, CA, USA
_______________________________________________
mpiwg-tools mailing list
mpiwg-tools at lists.mpi-forum.org<mailto:mpiwg-tools at lists.mpi-forum.org>
http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools
_______________________________________________
mpiwg-tools mailing list
mpiwg-tools at lists.mpi-forum.org<mailto:mpiwg-tools at lists.mpi-forum.org>
http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools
______________________________________________________________
Kathryn Mohror, kathryn at llnl.gov<mailto:kathryn at llnl.gov>, http://people.llnl.gov/mohror1
CASC @ Lawrence Livermore National Laboratory, Livermore, CA, USA
_______________________________________________
mpiwg-tools mailing list
mpiwg-tools at lists.mpi-forum.org<mailto:mpiwg-tools at lists.mpi-forum.org>
http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpi-forum.org/pipermail/mpiwg-tools/attachments/20130826/b8f7a21e/attachment-0001.html>
More information about the mpiwg-tools
mailing list