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

Update RAPIDS to use cuda::mr::async_resource_ref #16

Open
12 of 16 tasks
harrism opened this issue Jan 30, 2024 · 2 comments
Open
12 of 16 tasks

Update RAPIDS to use cuda::mr::async_resource_ref #16

harrism opened this issue Jan 30, 2024 · 2 comments
Assignees
Labels
breaking Introduces a breaking change

Comments

@harrism
Copy link
Member

harrism commented Jan 30, 2024

This is a cross-RAPIDS tracking issue for the epic described in this document. Please refer to the document for background and details.

Tasks

  1. 4 of 4
    cpp feature request tech debt
    harrism
  2. 3 of 3
    cpp feature request
    harrism
  3. feature request
    harrism
  4. feature request
    harrism
  5. 12 of 14
    feature request
  6. feature request
    harrism
  7. Java feature request
  8. improvement
  9. improvement
  10. improvement
  11. improvement
  12. improvement
  13. 9 of 13
    Epic feature request
    harrism miscco
@harrism harrism added the breaking Introduces a breaking change label Jan 30, 2024
@harrism harrism self-assigned this Jan 30, 2024
@harrism harrism changed the title Update RAPIDS to use cuda::mr::async_resource_ref and cuda::stream_ref Update RAPIDS to use cuda::mr::async_resource_ref Jan 30, 2024
@harrism
Copy link
Member Author

harrism commented Jan 30, 2024

#1443 includes much of this, but I've included all of the work here for cross-repo visibility.

@jakirkham
Copy link
Member

Have noted this as "In progress". Please let me know if that is not the case and can change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking Introduces a breaking change
Projects
Status: Todo
Development

No branches or pull requests

2 participants