mirror of
https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator.git
synced 2025-05-14 16:58:34 +00:00
Minor fixes in documentation of defragmentation
This commit is contained in:
parent
6a63f2cb4e
commit
20b9bc5334
2 changed files with 12 additions and 4 deletions
|
@ -17939,7 +17939,7 @@ enough free space, just scattered across many small free ranges between existing
|
|||
allocations.
|
||||
|
||||
To mitigate this problem, you can use defragmentation feature.
|
||||
It doesn't happen automatically thought and needs your cooperation,
|
||||
It doesn't happen automatically though and needs your cooperation,
|
||||
because VMA is a low level library that only allocates memory.
|
||||
It cannot recreate buffers and images in a new place as it doesn't remember the contents of `VkBufferCreateInfo` / `VkImageCreateInfo` structures.
|
||||
It cannot copy their contents as it doesn't record any commands to a command buffer.
|
||||
|
@ -17971,7 +17971,11 @@ for(;;)
|
|||
}
|
||||
//- Make sure the copy commands finished executing.
|
||||
//- Update appropriate descriptors to point to the new places.
|
||||
vmaEndDefragmentationPass(allocator, defragCtx, &pass);
|
||||
res = vmaEndDefragmentationPass(allocator, defragCtx, &pass);
|
||||
if(res == VK_SUCCESS)
|
||||
break;
|
||||
else if(res != VK_INCOMPLETE)
|
||||
// Handle error...
|
||||
}
|
||||
else
|
||||
// Handle error...
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue