There are (currently) no restrictions on what can happen in attribute callback functions. See Fab's presentation from several months ago (I don't remember when, exactly, but the meeting was in San Jose/Cisco) about all the problems w/ attributes -- this is one of them (unrestricted access in callback functions). On Mar 6, 2014, at 7:51 AM, "Balaji, Pavan" <[email protected]> wrote:
I’m pretty sure that’s not correct. You can have large collective ops and other operations in the callbacks. HDF5 and PETSc do all sorts of stuff in these callbacks.
— Pavan
On Mar 6, 2014, at 9:39 AM, Jim Dinan <[email protected]> wrote:
I believe that the copy and free attribute callbacks are intended to be local functions that deal with objects the user has attached as attributes, that might need to be copied or freed. Can't find text that confirms this explicitly, though..
On Wed, Mar 5, 2014 at 6:31 PM, Balaji, Pavan <[email protected]> wrote:
The endpoints proposal says that Comm_free is not fully synchronizing. What happens if I have an attribute callback on that communicator which does a Bcast? How will that work?
— Pavan
_______________________________________________ mpiwg-hybridpm mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-hybridpm
_______________________________________________ mpiwg-hybridpm mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-hybridpm
_______________________________________________ mpiwg-hybridpm mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-hybridpm
-- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/