Skip to content
Marc-Andre Hermanns edited this page Jan 24, 2019 · 1 revision

Participants

  • James Clark
  • Marc-Andre Hermanns
  • Jithin Jose

Topics

Leaving MPI_T_CB_REQUIRE_MPI_RESTRICTED as a separate level?

  • How would we communicate that other functions than our list are allowed?

  • Should we allow implementations to allow other functions?

  • How would a tool infer which functions are allowed?

    • No plans for an API for this in the first version of the API.

Enable additional MPI_T functions in callbacks

Feedback in the virtual meeting was generally positive on extending the list of supported functions. However, concerns were raised as not to overload the interface.

Should we have several classes?

E.g., MPI_T_event_read is mandatory (providing basic functionality)

Should we require calls on a specific CB level?

E.g., MPI_T_event_read needs to be available for every level, MPI_T_event_handle_alloc may be ok to be limited to lower levels.

Events interface

Functionname Include Minimum Level* Comment
MPI_T_EVENT_GET_NUM yes ?
MPI_T_EVENT_GET_INFO yes ?
MPI_T_EVENT_GET_INDEX yes ?
MPI_T_EVENT_HANDLE_SET_INFO yes ?
MPI_T_EVENT_HANDLE_GET_INFO yes ?
MPI_T_EVENT_SET_DROPPED_HANDLER yes ?

* Discussion on Minimum Levels required per function postponed

PVAR interface

Functionname Include Minimum Level* Comment
MPI_T_PVAR_GET_NUM yes ?
MPI_T_PVAR_GET_INFO yes ?
MPI_T_PVAR_GET_INDEX yes ?
MPI_T_PVAR_SESSION_CREATE maybe ? Does a tool need multiple sessions?
MPI_T_PVAR_SESSION_FREE maybe ? Does a tool need multiple sessions?
MPI_T_PVAR_HANDLE_ALLOC yes ?
MPI_T_PVAR_HANDLE_FREE yes ?

* Discussion on Minimum Levels required per function postponed

CVAR interface

Should we/can we include variables here? Callbacks are asynchronous on the different processes, thus coordination between processes may be hard/impossible.

  • Reading may be valuable for all scopes, writing should only be available for MPI_T_SCOREP_LOCAL.

Category interface

Should we include this for completeness?

  • Let's revisit this again after reading the Category section.

Handle dropped events

Feedback from Virtual Meeting was a bit scarce on this, but providing the source index as a parameter to the dropped callback seems the more flexible approach.

  • Choose option 2 (Source index delivered to Dropped Handler)
Clone this wiki locally