-
Notifications
You must be signed in to change notification settings - Fork 99
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
Why CrsMatrix::staticcrsgraph_type uses execution_space and not device_type? #665
Labels
Milestone
Comments
@brian-kelley I don't think so, I'm not sure who wrote the original code but I just checked the Kokkos StaticCrsGraph and the third template parameter is intended to be a DeviceType, not specifically an execution space. |
@ndellingwood OK, I'll change this to a bug and make a PR. |
brian-kelley
added a commit
to brian-kelley/kokkos-kernels
that referenced
this issue
Mar 24, 2020
for StaticCrsGraph typedef inside CrsMatrix. This is important for when the device type uses a different memory space than the default for the exec space (which Tpetra will want to do with CudaSpace soon).
Fix in #666 (ooh, the PR of the beast) |
ndellingwood
added a commit
that referenced
this issue
Mar 25, 2020
Fix #665 (Graph's device type inside CrsMatrix)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@ndellingwood In KokkosSparse_CrsMatrix.hpp, the graph type is defined using execution_space, not device_type. Is this intentional? I think it will need to be changed for Tpetra to remove UVM from CrsMatrix/CrsGraph, because when UVM is enabled as the default memory space for Kokkos::Cuda, it's not possible to instantiate KokkosSparse::CrsMatrix for device =
Device<Cuda, CudaSpace>
.The text was updated successfully, but these errors were encountered: