-
Notifications
You must be signed in to change notification settings - Fork 96
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
API: add explicit memory mapping #1037
base: master
Are you sure you want to change the base?
Conversation
@nsarka @janjust @Sergei-Lebedev @manjugv May be easier to discuss / track updates to API here. |
Can one of the admins verify this patch? |
src/ucc/api/ucc.h
Outdated
* | ||
* @return Error code as defined by @ref ucc_status_t. | ||
*/ | ||
ucc_status_t ucc_mem_exchange_post(ucc_mem_map_mem_h *memh); |
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.
@wfaderhold21 Is there a need to have an explicit call for exchanging memory handles? Why can't one use allgather or other collectives?
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.
@manjugv Fundamentally, this is an allgather collective. This explicitly has the UCC library perform the operation rather than the User. Is it better to have the User exchange the opaque structure?
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.
I don't see the value add, and need for explicit collective call.
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.
@manjugv removed the explicit collective.
What
Adds explicit mapping of user-provided memory for various TLs.