eden-emu/VulkanMemoryAllocator
19
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Updated documentation - added information about VK_AMD_memory_allocation_behavior extension.

Browse source 
Regenerated documentation, using new Doxygen version.
This commit is contained in:
Adam Sawicki 2019-01-15 11:45:58 +01:00
parent ae5c4661ec
commit 796cdc62f6
119 changed files with 1076 additions and 929 deletions
Download patch file Download diff file Expand all files Collapse all files

11
src/vk_mem_alloc.h
View file

@ -1495,7 +1495,16 @@ VmaAllocatorCreateInfo::pDeviceMemoryCallbacks.
\section heap_memory_limit Device heap memory limit
If you want to test how your program behaves with limited amount of Vulkan device
When device memory of certain heap runs out of free space, new allocations may
fail (returning error code) or they may succeed, silently pushing some existing
memory blocks from GPU VRAM to system RAM (which degrades performance). This
behavior is implementation-dependant - it depends on GPU vendor and graphics
driver.
On AMD cards it can be controlled while creating Vulkan device object by using
VK_AMD_memory_allocation_behavior extension, if available.
Alternatively, if you want to test how your program behaves with limited amount of Vulkan device
memory available without switching your graphics card to one that really has
smaller VRAM, you can use a feature of this library intended for this purpose.
To do it, fill optional member VmaAllocatorCreateInfo::pHeapSizeLimit.