-
Notifications
You must be signed in to change notification settings - Fork 200
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
Change device_scalar
to take async_resource_ref
#1447
Merged
rapids-bot
merged 6 commits into
rapidsai:branch-24.04
from
miscco:refactor_device_scalar
Feb 2, 2024
Merged
Change device_scalar
to take async_resource_ref
#1447
rapids-bot
merged 6 commits into
rapidsai:branch-24.04
from
miscco:refactor_device_scalar
Feb 2, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
miscco
force-pushed
the
refactor_device_scalar
branch
from
January 30, 2024 13:53
6288b8c
to
1db2eae
Compare
This rewrites `rmm::device_scalar` to take a `cuda::mr::async_resource_ref` instead of a plain `rmm::device_memory_resource*`. This is completely opaque to the user as the underlying `rmm::device_uvector` already takes a `cuda::mr::async_resource_ref` Addresses rapidsai#1446
miscco
force-pushed
the
refactor_device_scalar
branch
from
January 30, 2024 13:57
1db2eae
to
c7288cb
Compare
rongou
approved these changes
Jan 30, 2024
harrism
approved these changes
Jan 30, 2024
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.
Looks good. Thanks for finishing this low-hanging fruit!
If we merge this before #1441 we should update that PR to update this file.
harrism
changed the title
Move
ChangeJan 30, 2024
device_scalar
over to async_resource_ref
device_scalar
to take async_resource_ref
harrism
changed the title
Change
Change Jan 30, 2024
device_scalar
to take async_resource_ref
device_scalar
to take async_resource_ref
harrism
reviewed
Feb 1, 2024
/merge |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This rewrite
device_scalar
to takeasync_resource_ref
instead of a plaindevice_memory_resource*
. This is completely opaque to the user as the underlyingdevice_uvector
already takes aasync_resource_ref
Checklist
closes #1446