-
Notifications
You must be signed in to change notification settings - Fork 311
ch4/ucx: Use UCX datatypes in active message path #7538
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
base: main
Are you sure you want to change the base?
Conversation
|
test:mpich/ch4/ucx |
|
test:mpich/ch4/gpu/ucx |
|
Looks to be a bug in the setting of the received size of noncontig am recv, so dropped that part for now. |
092506d to
8899fa9
Compare
|
test:mpich/ch4/ucx |
|
whitespace checker has me in a blender 😦 |
|
test:mpich/ch4/ucx |
|
test:mpich/ch4/gpu/ucx |
Since we already have the request, we can always put it in the user_data parameter and avoid some complexity.
UCX has support for noncontig datatypes in the nbx active message send interface. Use it like we do in the tagged path.
|
test:mpich/ch4/gpu/ucx |
Pull Request Description
Splitting non-GPU commits from #6795 for testing.
Author Checklist
Particularly focus on why, not what. Reference background, issues, test failures, xfail entries, etc.
Commits are self-contained and do not do two things at once.
Commit message is of the form:
module: short descriptionCommit message explains what's in the commit.
Whitespace checker. Warnings test. Additional tests via comments.
For non-Argonne authors, check contribution agreement.
If necessary, request an explicit comment from your companies PR approval manager.