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

Fixing workaroun to cuSPARSE bug that was reverted during 24.02 release #2184

Closed
wants to merge 16 commits into from

Conversation

cjnolet
Copy link
Member

@cjnolet cjnolet commented Feb 14, 2024

This workaround was accidentally reverted during this commit but the additional memory copy is needed for proper results in CUDA 12.2-12.4.

@cjnolet cjnolet requested review from a team as code owners February 14, 2024 03:59
@cjnolet cjnolet self-assigned this Feb 14, 2024
@cjnolet cjnolet added bug Something isn't working non-breaking Non-breaking change and removed cpp python labels Feb 14, 2024
Co-authored-by: Paul Taylor <178183+trxcllnt@users.noreply.github.com>
// and incorrect results. This bug is fixed in CUDA 12.5+ so this workaround shouldn't be removed
// until that version is supported.
auto z_tmp = raft::make_device_matrix<ValueType, IndexType>(handle, z.extent(0), z.extent(1));
raft::copy(z_tmp.data_handle(), z.data_handle(), z.size(), raft::resource::get_cuda_stream(handle));
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixes style checker:

Suggested change
raft::copy(z_tmp.data_handle(), z.data_handle(), z.size(), raft::resource::get_cuda_stream(handle));
raft::copy(
z_tmp.data_handle(), z.data_handle(), z.size(), raft::resource::get_cuda_stream(handle));

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mfoerste4's PR 2185 uses an intermediate device_uvector instead of a raft::device_matrix because the matrix's size() isn't suitable for the copy here.

That PR is targeting branch-24.02. Should we merge that PR into 24.02 and rerelease RAFT, or should we merge that PR into this one and include it in 24.04?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working cpp non-breaking Non-breaking change python
Projects
Development

Successfully merging this pull request may close these issues.

None yet

4 participants