-
Notifications
You must be signed in to change notification settings - Fork 919
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
[FEA] Add support for CUDA 11 #5369
Comments
Regarding 3) above: this is fixed by getting a more recent jitify. We need to update rapidsai/jitify to the latest from NVIDIA/jitify. The next issue I ran into was when building the libcudf python bindings, I get errors like this:
This is because it looks for cub in thirdparty before the toolkit. If we fetch both CUB and thrust together in #5315 we should make sure they are always compatible. |
I fixed the CUB/Thrust incompatibility error locally by commenting out this line: Line 47 in 06213db
With this cuDF Cython compiles and all pytests pass. |
Numba related fixes are here: numba/numba#5819 |
CuPy CUDA 11 PR: cupy/cupy#3405 |
Leaving this open until the corresponding Numba / CuPy PRs are merged. |
@kkraus14 Numba and CuPy PRs are merged. Closing. Reopen if there are still blockers. But I believe cuDF works with CUDA 11 now. |
CuPy 8 won't be released before RAPIDS 0.15. There's currently some work being done to backport CUDA 11.0 to 7.8.0 but there are still issues that we're trying to track down and fix. |
The expected release date for CuPy 7.8.0 is August 19th, a week before RAPIDS 0.15. |
Any idea about the support of CUDA 11.1 ? |
We are currently exploring our options in supporting CUDA 11.1 and greater with CUDA Enhanced Compatibility (https://docs.nvidia.com/deploy/cuda-compatibility/index.html#enhanced-compat-minor-releases). There are no immediate plans to directly support CUDA 11.1. |
Is there any workaround to make this run on NVIDIA RTX 3090? I tried linking libnvrtc.so.11.0 libnvrtc.so.11.1.
|
You can use CUDA 11.0 on an RTX 3090. The So you need a newer driver in order to support the RTX 3090, but you should be fine with the CUDA 11.0 toolkit / libraries. If that doesn't work please report back. |
Is your feature request related to a problem? Please describe.
This issue is for tracking issues building and running cuDF with CUDA 11, and any fixes required.
Currently testing with a prerelease of CUDA 11.0. Issues:
CUB is now part of the CUDA toolkit, and cmake is finding CUB there before the submodule in thirdparty. The newer version in the toolkit changed the API ofThis was all resolved by [REVIEW] fetch thrust/cub from github #5315cub::ShuffleIndex
, used in join_kernels.cuh. The fix is easy, but is dependent on [REVIEW] fetch thrust/cub from github #5315 . If we update to the latest CUB, we need to change join_kernels.cuh. If we do not, we can reorder paths in CMakeLists.txt to favorthirdparty
over the toolkit.Conda does not yet have a cudatoolkit=11.0 package (naturally). This is not a problem when just building libcudf, but may cause problems with testing Python. Edit: Python testing seems to work with conda cudatoolkit=10.2, but wheels are in motion to produce an 11.0 metapackage.
On first build and test (after fixing Collaborations on columnar data structures #1 above locally), I get these gtest failures.
Edit: this will be resolved by merging the latest from jitify into the rapidsai/jitify fork.
The text was updated successfully, but these errors were encountered: