Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[CUDA] Add support for cuSparse #25

Open
jasonsewall-intel opened this issue Jun 15, 2020 · 4 comments · May be fixed by #527
Open

[CUDA] Add support for cuSparse #25

jasonsewall-intel opened this issue Jun 15, 2020 · 4 comments · May be fixed by #527
Assignees
@Rbiessy
Labels
accepted The issue/feature is confirmed and going to be implemented API A request to add/change/fix/improve the API backend A request to enable new implementation behind API

Comments

@jasonsewall-intel
Copy link

oneMKL provides support for sparse BLAS operations, and NVIDIA provides an interface to sparse BLAS operations optimized for their hardware in the cuSparse library. Much as oneMKL provides support for cuBLAS, I propose it add support for cuSparse.

The unified interface provided by oneMKL will be much more convenient for users interested in performance portability across platform sets that include NVIDIA GPUs.

The mechanisms and design work that are relevant for cuBLAS are likely to be reusable for this work. Because sparse interfaces are generally younger and more flexible, it may be that this is best done incrementally.
@jasukhar
Copy link
Contributor

Hi @jasonsewall-intel!
oneMKL open source project doesn't contain at this moment Sparse interfaces, but we plan to add them in the future. With that cuSparse can be enabled under DPC++ APIs similarly as it was done for cuBLAS. We also encourage to contribute to open source and help us enable new interfaces, libraries and HWs. If you are interested, we can inform you once Sparse DPC++ APIs are available.

@jasukhar jasukhar added API A request to add/change/fix/improve the API backend A request to enable new implementation behind API accepted The issue/feature is confirmed and going to be implemented labels Jun 15, 2020
@abagusetty
Copy link

Hi @jasukhar One of the library (Hypre) with SYCL backend wanted to tap into oneMKL cuSparse support and wanted to check if there were plans to support cuSolver

@mmeterel
Copy link
Contributor

mmeterel commented Feb 9, 2023

Tagging @spencerpatty

@spencerpatty
Copy link

The first step would be to add Sparse BLAS APIs to the current oneMKL Interfaces project. Once that is done,  it should be straightforward to add cuSparse support. While we won't be adding sparse APIs in the near term due to other priorities, we encourage anyone who is interested to contribute to this open source project and to help enable new interfaces, libraries and HWs as needed.

@Rbiessy Rbiessy self-assigned this Feb 6, 2024
@Rbiessy Rbiessy linked a pull request Jul 4, 2024 that will close this issue
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Rbiessy Rbiessy

Labels
accepted The issue/feature is confirmed and going to be implemented API A request to add/change/fix/improve the API backend A request to enable new implementation behind API
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[SPARSE] Add support for cuSPARSE backend Rbiessy/oneMKL
6 participants
@jasonsewall-intel @Rbiessy @mmeterel @jasukhar @spencerpatty @abagusetty