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

Clarification of hipMallocManaged memory placement (GPU or CPU on Frontier/Crusher) #3197

Open
bgoglin opened this issue Mar 30, 2023 · 2 comments

Comments

@bgoglin
Copy link

bgoglin commented Mar 30, 2023

Hello
I was reading the OLCF documentation of Frontier/Crusher systems and got confused by section "HSA_XNACK=0 Automatic Page Migration Disabled" on page https://docs.olcf.ornl.gov/systems/crusher_quick_start_guide.html#notable-differences-between-summit-and-crusher
Second line of the table says that hipMallocManaged() initially allocates on CPU DDR4, and then CPU accesses are "Zero copy read/write over Infinity Fabric" while GPU accesses are "Local read/write". Wait, migration is disabled in this case so memory won't ever move to GPU HBM. Hence GPU access shouldn't be "local read/write" but rather "Zero copy read/write over Infinity Fabric" (and the contrary of CPU access).
Or is the memory initially allocated on GPU when using hipMallocManaged() ?
Thanks
Brice

@ppanchad-amd
Copy link

@bgoglin Internal ticket has been created to provide clarification? Thanks!

@bgoglin
Copy link
Author

bgoglin commented Apr 11, 2024

@ppanchad-amd Thanks, can you post some clarification here in the meantime?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants