-
Notifications
You must be signed in to change notification settings - Fork 201
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
Rename cuda::experimental::managed_memory_resource
to cuda::experimental::unified_memory_resource
#4094
Comments
@jrhemstad @ericniebler Who is the right person to see this? |
We can happily rename it |
This renames the `managed_memory_resource` to `unified_memory_resource`. While we are at it also add the classes to our documentation. Fixes NVIDIA#4093 Fixes NVIDIA#4094
The lack of clarity in naming here comes up often for RMM users. Docs should mention both names with any technical details about how they differ. I believe there are some subtleties that we should make sure we understand and can teach users before renaming this. |
CCCL docs should definitely mention all terms in use: Unified Memory, UVM, Managed Memory. Somewhere we should also explain HMM/ATS. We need an explainer for this whole feature somewhere. Blog post maybe. |
I would also be fine with exposing multiple names via aliases. |
In the PR I am linking to https://developer.nvidia.com/blog/unified-memory-cuda-beginners/ Any other blogs that would make sense? |
"Managed memory" is a terrible and unclear name for the CUDA Unified Memory feature, and it may be particularly confusing to C++ users, as there is an existing, deprecated, and terrible thing called "Managed C++".
C++ people don't like things that are "managed"; people write C++ because they want control. This name makes Unified Memory sound like a scary black box with perf issues. Couple that with the fact that historically Unified Memory has had perf issues, and the name sounds the wrong sort of message.
We can't rename
cudaMallocManaged
, but we don't have to repeat the mistake. Please call itcudax::experimental::unified_memory_resource
notcudax::experimental::managed_memory_resource
.The text was updated successfully, but these errors were encountered: