search

rapidsai / rmm

RAPIDS Memory Manager
https://docs.rapids.ai/api/rmm/stable/
Apache License 2.0
477 stars 195 forks source link

Refactor RMM resources to implement `cuda::memory_resource` concepts and deprecate and remove `device_memory_resource` and `host_memory_resource` base classes. #1445

Open harrism opened 8 months ago

harrism commented 8 months ago

Part of #1443 

### Tasks that should not require prior work
- [ ] https://github.com/rapidsai/rmm/issues/1446
- [ ] https://github.com/rapidsai/rmm/issues/1448
- [ ] https://github.com/rapidsai/rmm/issues/1453
- [x] Add `rmm::device_check_resource_adaptor::get_upstream_resource`
- [ ] https://github.com/rapidsai/rmm/issues/1450
- [ ] https://github.com/rapidsai/rmm/issues/1481
- [ ] https://github.com/rapidsai/rmm/issues/1455
### Tasks that would remove APIs that return a `device_memory_resource`
- [ ] https://github.com/rapidsai/rmm/issues/1540
- [ ] https://github.com/rapidsai/rmm/issues/1541
- [ ] https://github.com/rapidsai/rmm/pull/1491
- [ ] https://github.com/rapidsai/rmm/issues/1500
### Final tasks that will have considerable downstream effects
- [ ] https://github.com/rapidsai/rmm/issues/1596
- [ ] https://github.com/rapidsai/rmm/issues/1457
harrism commented 8 months ago

For the ones with downstream effects we should build the new solution beside the existing one, then switch the downstream to the new, then deprecate the old, then in the following release remove the deprecated functionality.