-
Notifications
You must be signed in to change notification settings - Fork 529
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
[Issue]: hipMalloc()
allocations over 4GB redirected to shared GPU memory
#3644
Comments
Hi @7shi, an internal ticket has been created to investigate this. Thanks! |
Hi @7shi, I cannot reproduce the problem. Can you verify that you have the latest version 24.10.16 of the display driver? |
Hi @zichguan-amd, Thank you for your response. I updated my driver from 24.9.1 to 24.10.1 (latest available version), but the issue still persists. Note that I couldn't locate version 24.10.16 you mentioned. For background context (outside the scope of this issue): I initially encountered this while investigating LLM performance issues in my environment. After investigation, I traced the root cause to this |
I was informed that this issue doesn't occur in 24.8.1, but appears in both 24.9.1 and 24.10.1. The version 24.10.16 you mentioned doesn't seem to be publicly available yet, but I hope it will be fixed in that release. |
I can confirm this issue with Adrenalin 24.10.1 and 24.9.1. I'll look into it. Changing the driver should fix this. You can either downgrade to Adrenalin 24.8.1, or use the latest Pro edition driver that comes bundled with HIP sdk, which is 24.Q2 or 24.10.16 that I mentioned in the previous comment. |
Thank you for investigating this issue and providing the workarounds. I've confirmed that I wasn't aware that Pro drivers could be used with Radeon RX. I've tested 24.Q2 and can confirm it works correctly. While I couldn't figure out how to obtain 24.10.16, I plan to use 24.Q2 for now. Since most users would typically install Adrenalin, I hope this issue will be resolved in future versions. |
Problem Description
While testing memory allocation using
hipMalloc()
in a HIP environment, I observed an unexpected behavior when attempting to allocate large chunks of memory.Key Observations:
hipMalloc()
call result in the allocation being redirected to shared GPU memory instead of dedicated VRAM.Implications:
This behavior could significantly impact performance for applications requiring large memory allocations, as shared GPU memory is typically slower than dedicated VRAM.
Operating System
Windows 11 Home (10.0.22631)
CPU
AMD Ryzen 5 5600X 6-Core Processor
GPU
AMD Radeon RX 7600 XT
ROCm Version
ROCm 6.1.0
ROCm Component
HIP
Steps to Reproduce
I used a C++ program that incrementally allocates memory using
hipMalloc()
, starting from 512MB and increasing by 512MB increments up to 4GB and beyond. The program monitors the success of each allocation and the type of memory used.Result:
(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
No response
Additional Information
hipconfig --full
The text was updated successfully, but these errors were encountered: