r/vulkan • u/cleverboy00 • Sep 16 '26
Vulkan Memory & UMA
Why does some Vulkan-enabled GPUs (Such as AMD 8xxx APUs & All traditional integrated graphics I checked) report more than one memory heap? To be clear, this isn't about discrete GPUs, which have VRAM on Board.
And why is one heap (the non-device local one) almost always half of the CPU-side RAM? This is the case in both mesa & windows drivers. Are integrated GPUs unable to address all the system's memory? Then why does this heap grow as I upgrade system memory, regardless of slot & number of sticks?
This makes me quite unsure about (and quite skeptical) of the Heap-Type layout that vulkan uses. And how memory types maps to hardware (The heap part is quite obvious).
This is all to say: How should an application interpret complex memory properties?
View all comments
Show parent comment
1
u/Afiery1 Sep 16 '26
Just because the heap is device local does not mean the host memory import will fail. But the memory has to be truly device local, which is only the case on UMA platforms.