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.

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

[Lang] Support LU sparse solver on CUDA backend #6967

Merged
merged 13 commits into from
Dec 26, 2022

Conversation

FantasyVR
Copy link
Collaborator

@FantasyVR FantasyVR commented Dec 23, 2022

Issue: #2906

Brief Summary

To be consistent with API on CPU backend, this pr provides LU sparse solver on CUDA backend. CuSolver just provides a CPU version API of LU sparse solver which is used in this PR. The cuSolverRF provides a GPU version LU solve, but it only supports double datatype. Thus, it's not used in this PR.

Besides, the print_triplets is refactored to resolve the ndarray read constraints (the read and write data should be the same datatype).

@netlify
Copy link

netlify bot commented Dec 23, 2022

Deploy Preview for docsite-preview ready!

Name Link
🔨 Latest commit e01ac23
🔍 Latest deploy log https://app.netlify.com/sites/docsite-preview/deploys/63a5383349606e0008c91e13
😎 Deploy Preview https://deploy-preview-6967--docsite-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@FantasyVR FantasyVR merged commit fc6931f into taichi-dev:master Dec 26, 2022
@FantasyVR FantasyVR deleted the lu branch December 27, 2022 02:08
quadpixels pushed a commit to quadpixels/taichi that referenced this pull request May 13, 2023
Issue: taichi-dev#2906 

### Brief Summary
To be consistent with API on CPU backend, this pr provides LU sparse
solver on CUDA backend. CuSolver just provides a CPU version API of LU
sparse solver which is used in this PR. The cuSolverRF provides a GPU
version LU solve, but it only supports `double` datatype. Thus, it's not
used in this PR.

Besides, the `print_triplets` is refactored to resolve the ndarray
`read` constraints (the `read` and `write` data should be the same
datatype).

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants