I had to go back and read about generalized requests to remind myself how they worked... But now I agree with Fab. They won't work as timers except in THREAD_MULTIPLE + multiple threads scenarios. So I think that the timers-as-requests idea still stands... On Mar 7, 2011, at 3:49 PM, Fab Tillier wrote:
Jeff Squyres wrote on Mon, 7 Mar 2011 at 12:31:41
Dave's point about generalized requests is a good one, though -- I need to go think about that and convince myself that what we're talking about isn't syntactic sugar and/or why it's better to be in the MPI implementation.
In a MPI_THREAD_SERIALIZED implementation, you can't use call MPI_GREQUEST_COMPLETE if you're already calling MPI_WAITANY. Depending on generalized requests would require MPI_THREAD_MULTIPLE support for this functionality.
Note that for some implementations, making MPI_GREQUEST_COMPLETE thread-safe could be trivial, but there's no MPI_THREAD_MOSTLY_SERIALIZED option so there's no standard way of noting that some things are thread safe while others are not - it's either all or nothing.
-Fab
_______________________________________________ Mpi3-bwcompat mailing list Mpi3-bwcompat_at_[hidden] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-bwcompat
-- Jeff Squyres jsquyres_at_[hidden] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/