Notes 2016 07 21
Marc-Andre Hermanns edited this page Aug 5, 2016
·
2 revisions
- Jean-Baptiste Besnard
- Marc-Andre Hermanns
- Kathryn Mohror
- Martin Schulz
- ...
- Discussion of the initial draft of
mpi_t_events.h - The file lives in a Git repository at RWTH Aachen University
- Let Marc-Andre know, if you need access
- Synchronicity should not be handles as an event class but as a flag in the event information
- Should this be a separate parameter of within a flag bitfield?
- Prefix for calls should be
MPI_T_event_ - Do we need sessions? If we use individual event handles this might not be necessary
- Should event registration block or not?
- Should we return a "postponed" error code?
- Should event de-registration block or not? When is it safe for the user to de-allocate the user_data pointer?
- Sequential reading of information from the event handle, entry by entry