mirror of
https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator
synced 2024-12-26 10:51:01 +00:00
Small fix in documentation.
This commit is contained in:
parent
0845f1c2e5
commit
9e1684f87a
@ -143,7 +143,10 @@ Custom memory allocator</h1>
|
|||||||
<p>You can use custom memory allocator by filling optional member <a class="el" href="struct_vma_allocator_create_info.html#a6e409087e3be55400d0e4ccbe43c608d" title="Custom allocation callbacks. ">VmaAllocatorCreateInfo::pAllocationCallbacks</a>. These functions will be passed to Vulkan, as well as used by the library itself to make any CPU-side allocations.</p>
|
<p>You can use custom memory allocator by filling optional member <a class="el" href="struct_vma_allocator_create_info.html#a6e409087e3be55400d0e4ccbe43c608d" title="Custom allocation callbacks. ">VmaAllocatorCreateInfo::pAllocationCallbacks</a>. These functions will be passed to Vulkan, as well as used by the library itself to make any CPU-side allocations.</p>
|
||||||
<h1><a class="anchor" id="thread_safety"></a>
|
<h1><a class="anchor" id="thread_safety"></a>
|
||||||
Thread safety</h1>
|
Thread safety</h1>
|
||||||
<p>All calls to functions that take VmaAllocator as first parameter are safe to call from multiple threads simultaneously, synchronized internally when needed. </p>
|
<ul>
|
||||||
|
<li>The library has no global state, so separate VmaAllocator objects can be used independently.</li>
|
||||||
|
<li>All calls to functions that take VmaAllocator as first parameter are safe to call from multiple threads simultaneously because they are synchronized internally when needed. </li>
|
||||||
|
</ul>
|
||||||
</div></div><!-- contents -->
|
</div></div><!-- contents -->
|
||||||
<!-- start footer part -->
|
<!-- start footer part -->
|
||||||
<hr class="footer"/><address class="footer"><small>
|
<hr class="footer"/><address class="footer"><small>
|
||||||
|
File diff suppressed because one or more lines are too long
@ -144,8 +144,12 @@ Vulkan, as well as used by the library itself to make any CPU-side allocations.
|
|||||||
|
|
||||||
\section thread_safety Thread safety
|
\section thread_safety Thread safety
|
||||||
|
|
||||||
All calls to functions that take VmaAllocator as first parameter are safe to
|
- The library has no global state, so separate VmaAllocator objects can be used
|
||||||
call from multiple threads simultaneously, synchronized internally when needed.
|
independently.
|
||||||
|
- All calls to functions that take VmaAllocator as first parameter are safe to
|
||||||
|
call from multiple threads simultaneously because they are synchronized
|
||||||
|
internally when needed.
|
||||||
|
|
||||||
*/
|
*/
|
||||||
|
|
||||||
#include <vulkan/vulkan.h>
|
#include <vulkan/vulkan.h>
|
||||||
|
Loading…
Reference in New Issue
Block a user