AuroraMiddleware/VulkanMemoryAllocator
1
0
Fork 0
mirror of https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator synced 2024-12-26 02:41:01 +00:00
Code Issues Projects Releases Wiki Activity

Small fix in documentation.

Browse Source
This commit is contained in:
Adam Sawicki 2017-07-11 15:27:08 +02:00
parent 0845f1c2e5
commit 9e1684f87a
3 changed files with 46 additions and 39 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/html/index.html
View File

@ -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>
<h1><a class="anchor" id="thread_safety"></a>
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 -->
<!-- start footer part -->
<hr class="footer"/><address class="footer"><small>

72
docs/html/vk__mem__alloc_8h_source.html
View File

File diff suppressed because one or more lines are too long

8
src/vk_mem_alloc.h
View File

@ -144,8 +144,12 @@ Vulkan, as well as used by the library itself to make any CPU-side allocations.
\section thread_safety Thread safety
All calls to functions that take VmaAllocator as first parameter are safe to
call from multiple threads simultaneously, synchronized internally when needed.
- The library has no global state, so separate VmaAllocator objects can be used
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>