mirror of
https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator.git
synced 2025-05-28 23:49:21 +00:00
Updated documentation regarding dedicated allocations in custom pools
Regenerated the documentation.
This commit is contained in:
parent
4586be47d8
commit
0109967554
12 changed files with 72 additions and 68 deletions
include
|
@ -506,8 +506,6 @@ typedef enum VmaAllocationCreateFlagBits
|
|||
/** \brief Set this flag if the allocation should have its own memory block.
|
||||
|
||||
Use it for special, big resources, like fullscreen images used as attachments.
|
||||
|
||||
You should not use this flag if VmaAllocationCreateInfo::pool is not null.
|
||||
*/
|
||||
VMA_ALLOCATION_CREATE_DEDICATED_MEMORY_BIT = 0x00000001,
|
||||
|
||||
|
@ -1162,6 +1160,7 @@ typedef struct VmaPoolCreateInfo
|
|||
|
||||
Leave 0 to use default and let the library manage block sizes automatically.
|
||||
Sizes of particular blocks may vary.
|
||||
In this case, the pool will also support dedicated allocations.
|
||||
*/
|
||||
VkDeviceSize blockSize;
|
||||
/** \brief Minimum number of blocks to be always allocated in this pool, even if they stay empty.
|
||||
|
@ -19487,6 +19486,11 @@ vmaDestroyBuffer(allocator, buf, alloc);
|
|||
vmaDestroyPool(allocator, pool);
|
||||
\endcode
|
||||
|
||||
New versions of this library support creating dedicated allocations in custom pools.
|
||||
It is supported only when VmaPoolCreateInfo::blockSize = 0.
|
||||
To use this feature, set VmaAllocationCreateInfo::pool to the pointer to your custom pool and
|
||||
VmaAllocationCreateInfo::flags to #VMA_ALLOCATION_CREATE_DEDICATED_MEMORY_BIT.
|
||||
|
||||
\section custom_memory_pools_MemTypeIndex Choosing memory type index
|
||||
|
||||
When creating a pool, you must explicitly specify memory type index.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue