You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jasonsewall-intel opened this issue
Jun 15, 2020
· 4 comments
· May be fixed by #527
Assignees
Labels
acceptedThe issue/feature is confirmed and going to be implementedAPIA request to add/change/fix/improve the APIbackendA request to enable new implementation behind API
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.
The text was updated successfully, but these errors were encountered:
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
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
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
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.
acceptedThe issue/feature is confirmed and going to be implementedAPIA request to add/change/fix/improve the APIbackendA request to enable new implementation behind API
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.
The text was updated successfully, but these errors were encountered: