-
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
sptrsv: Add tplchain and cusparse #555
Conversation
Spot-check on kokkos-dev-2: Failure with Cuda_OpenMP, currently testing fix
|
How does this relate to #552 ? Are they meant to happen together or should they be sequenced? |
@mhoemmen they can be sequenced, I'll have to fix merge conflicts when they're ready for merge but the functionalities are independent of one another. |
I'm going to have to push an extra change shortly here, getting the cudagraph stuff to work with Kokkos is more fragile than I anticipated, see kokkos/kokkos#2606 |
I'll push the cudagraph fix in a moment when the test finishes. |
kh.get_sptrsv_handle()->print_algorithm(); | ||
break; | ||
*/ | ||
#ifdef KOKKOSKERNELS_ENABLE_TPL_CUSPARSE | ||
case CUSPARSE: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ndellingwood could you please remind me what different between CUSPARSE
and CUSPARSE_K
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question - CUSPARSE_K is the kokkos-kernels supported version I added in the PR, CUSPARSE is the hand-rolled implementation within the perf test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How do CUSPARSE_K and CUSPARSE compare in terms of perf? Should we still need to keep CUSPARSE case in the perf test when we already have CUSPARSE_K?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't compared carefully, they should be nearly the same. It may be interesting to keep for comparison, but I can also remove to clean up the perf test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Understand. It is up to you to remove it or not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @vqd8a for the catch, I'll leave it in for now to comparison test but will clean up in a PR shortly after.
cudagraph support paired with Kokkos usage seems to be somewhat fragile keeping the code so it can be re-enabled as default once resolved
Rerun cuda tests on kokkos-dev-2:
|
No description provided.