-
Notifications
You must be signed in to change notification settings - Fork 2
Notes 2016 05 26
Marc-Andre Hermanns edited this page Jun 7, 2016
·
1 revision
- Jean-Baptiste Besnard
- Marc-Andre Hermanns
- Natahn Hjelm
- Kathryn Mohror
- Soren Rasmussen
MPI_T Events
- How to communicate type signatures of returned event information?
- We probably need a pack/unpack mechanism.
- Should we use existing MPI_PACKED types?
- Would an array of basic MPI datatypes suffice?
- Should there be some
basic
information that is communicated on every event?- If implementation does not provide the specific field a controlled
undefined
value could be provided. - Would the
extended
info then be communicated as a 'packed' buffer or would it be a 'padded' struct?
- If implementation does not provide the specific field a controlled
- Initialization
-
MPI_T_init_thread
should be sufficient
-
- How to bind Events to specific objects?
- What about tracking events within
MPI_Init
, e.g.,MPI_COMM_WORLD
? - Do we need a special mechanism to attach in these situations?
- What about tracking events within
- Grouping of events
- Should something like a
group_id
orchaid_id
identify events that preceed/succeed each other?
- Should something like a