-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
UCX 1.14.0 packages make CUDA optional #119
Comments
I have no idea how these improvements should affect the openmpi package. @leofang ? |
Think it comes down to changing this... openmpi-feedstock/recipe/meta.yaml Lines 47 to 48 in dfc3d61
...to this... - ucx # [enable_cuda] Though Tried playing with some changes to capture this in PR ( #121 ). Though there may be other valid approaches Would defer to Leo and you on what makes the most sense here 🙂 |
@jakirkham @minrk Please help me decide what to do in #128.
|
BTW, I brancked off |
Sorry I completely missed this. Why can't # the actual content would be more convolved due to the need of supporting CUDA 11 & 12,
# as they have different package layout. This is for illustration only.
run_constrained:
- cudatoolkit Once we decide how to approach this, I can take care of the CUDA part. |
I support "backporting" whatever decision that we land to the |
Maybe we will have to do it anyway. v5.0.x has changed the way they do things by default, components are no longer built as plugins, but rather linked to |
Closing. In #128 we use UCX unconditionally. |
Thanks all! 🙏 |
As part of the UCX 1.14.0 upgrade ( conda-forge/ucx-split-feedstock#111 ), CPU & GPU builds were merged making
cudatoolkit
optional anducx-proc
unneeded. So it should be possible to use UCX more generallyThe text was updated successfully, but these errors were encountered: