-
Notifications
You must be signed in to change notification settings - Fork 53
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
NOMERGE: Add bare-minimum Session API from proposal draft #1065
base: main
Are you sure you want to change the base?
Conversation
mpp/shmem-def.h.in
Outdated
#define SHMEM_SESSION_OP_AMO (1l<<3) | ||
#define SHMEM_SESSION_OP_AMO_FETCH (1l<<4) | ||
#define SHMEM_SESSION_CHAIN (1l<<5) | ||
#define SHMEM_SESSION_UNIFORM_AMO (1l<<6) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason we are not using _OP_
for the last two? No issue with the naming, I just want to understand if there is a reason.
/* Session Routines */ | ||
SHMEM_FUNCTION_ATTRIBUTES void SHPRE()shmem_session_start(long options, shmem_ctx_t ctx); | ||
SHMEM_FUNCTION_ATTRIBUTES void SHPRE()shmem_session_stop(shmem_ctx_t ctx); | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might have to move them to shmemx later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
eba3fbd
to
781d881
Compare
This is an example of bare-minimum support for the OpenSHMEM Sessions proposal (openshmem-org/specification#493). It's a work-in-progress, and we might prefer to put it in
shmemx
, depending on committee feedback and the spec release timeline.