Threads WG Meeting 12 10 2019

Agenda

Discussions related to Memory Spaces Proposal from #256 (https://github.com/openshmem-org/specification/pull/256) and #195 (https://github.com/openshmem-org/specification/issues/195)
Why do we need to separate Memory Spaces proposal into two parts - introducing Memory Spaces and then introduce support for different kinds of memory

Recap on what is Memory Spaces and Why do we need to support Team-based SHEAP
Proposed two different options for introducing Memory Spaces in OpenSHMEM
Option:1 extend shmem_team_config_t structure to include SHEAP information
Option:2 introduce new APIs and decouple team-creation and space-creation operations
Discussed pros and cons on the two design options
Min Si suggested to change the names of the new APIs in Option:2 to include Teams

Do we need to support multiple SHEAPs in a Team?
Do we need to support the semantics where child team can access parent teams space?
Do we need to break compatibility in the shmem_team_create_ctx API?