-
Notifications
You must be signed in to change notification settings - Fork 24
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
Adding CUDA-X #96
Comments
More information: the CUDA-X libraries, part of the RAPIDS project, are C/C++ libraries that use CUDA to talk to the GPU. For example cuGraph, a graph database component of CUDA-X, is built as a shared library, and then Python and Java bindings are added for the user level API. This appears to be just what cl-cuda does for the base CUDA library (adds a Common Lisp user level API). Given this architecture:
It seems that something at the same level as the cl-cuda.api, that makes use of cl-cuda.lang might be most the most appropriate place to add a cl-cuGraph API? @takagi, any thoughts on how to approach this? If there is anyway to reuse parts of cl-cuda, that's obviously the best solution. |
Hi. While I'm not sure about the detail of CUDA-X's API, I suppose that a reasonable approach is to define CFFI entries for CUDA-X API as cl-cuda.driver-api does for CUDA driver API as well as to provide some features for convenience in cl-cuda.api. |
This issue is to discuss CUDA-X, and how it might work with cl-cuda. From the architecture diagram, it appears that the CUDA-X libraries are built on top of CUDA.
Would it make sense to have cl-cuda include CUDA-X functionality? Or, would it be better to apply the same techniques in cl-cuda and write a separate library for CUDA-X that ran on top of cl-cuda, following the NVIDIA architecture?
The text was updated successfully, but these errors were encountered: