Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@koarakawaii
Copy link
Contributor

@koarakawaii koarakawaii commented Nov 9, 2025

  • Some properties for cudaDeviceProp are deprecated in CUDA 13.0; I did not check all of them, but only modified those affecting the compilation. See https://docs.nvidia.com/cuda/cuda-runtime-api/structcudaDeviceProp.html#structcudaDeviceProp for details.
    • Can consider switching the cudaDeviceGetAttribute API; but again, I did not check whether it covers all the properties we queried for cudaDeviceProp
  • Add configure file spock_intel_RTX5090.config for RTX5090 on spock26, which uses private NVIDIA HPC SDK modules instead of public CUDA on the log-in node. The path should be directing to public CUDA 13.0 when available, if we want to install it.
    • CUDA 12.1 also works for current driver version 580.95.05, but I am not sure we want to fall back to CUDA 12.1 if a more advanced version has been released.

@hyschive hyschive requested a review from xuanweishan November 15, 2025 13:57
@hyschive hyschive added enhancement gpu GPU issues and implementation labels Nov 15, 2025
@xuanweishan
Copy link

@koarakawaii Do you think we need to install cuda13 and nvidia hpc to spock:/software? So that the config no longer need to depend to your own file.

@koarakawaii
Copy link
Contributor Author

@xuanweishan : I think that will be great. I guess we will need it in the future anyway~

@xuanweishan
Copy link

It seems good to me.
I tried tests on both eureka and spock:

  • eureka 2080super(cuda12)
  • spock 3080ti(cuda12)
  • spock 5090(cuda13)
  • spock 3080ti(cuda13)(With modify config file for 3080 ti)
    All works properly.
    I think this PR is ready to merge after resolved the conflicts.

@koarakawaii
Copy link
Contributor Author

@xuanweishan : conflicts have been solved~

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement gpu GPU issues and implementation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants