Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Context: Adapt RMA and AMO with team/context #91

Open
2 tasks
minsii opened this issue Feb 26, 2021 · 0 comments
Open
2 tasks

Context: Adapt RMA and AMO with team/context #91

minsii opened this issue Feb 26, 2021 · 0 comments
Labels
Milestone

Comments

@minsii
Copy link
Collaborator

minsii commented Feb 26, 2021

Description: Once a team is created, the user can create a context with the team via SHMEM_TEAM_CREATE_CTX. The context means a set of local communication resource, similar to an MPI VCI. The context will then be used with any RMA or atomics (AMO) operation. When a team-context is used, the dest PE of each RMA or AMO operation needs to be read as team-relative PE, similar to the win-relative target_rank in MPI RMA.

Suggested implementation

# updates the comm based implementation as posted in #36
# For each team, creates `num_contexts` (>=0) number of wins at team creation time.
# It is safe to call win_create here as team creation is also collective.
SHMEM_TEAM_SPLIT_STRIDED
SHMEM_TEAM_SPLIT_2D

SHMEM_TEAM_CREATE_CTX -> return previously created win (local op)
SHMEM_CTX_GET_TEAM-> return associated team object (local op)

TODO

  • Implement SHMEM_TEAM_CREATE_CTX. Can skip optimization with SHMEM_CTX_SERIALIZED | SHMEM_CTX_PRIVATE | SHMEM_CTX_NOSTORE for now.
  • Update remote PE in all RMA and AMO operations by using team-relative PE.
@minsii minsii changed the title Team: Adapt RMA and AMO with teams Team: Adapt RMA and AMO with team/context Feb 26, 2021
@minsii minsii changed the title Team: Adapt RMA and AMO with team/context Context: Adapt RMA and AMO with team/context Feb 26, 2021
@minsii minsii added this to the FY21 milestone Feb 26, 2021
@minsii minsii modified the milestones: FY21-Q1Q2, FY21-Q3Q4 Mar 3, 2021
@minsii minsii removed the optional label Mar 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant