// Copyright (c) 2014-2016 Khronos Group. This work is licensed under a // Creative Commons Attribution 4.0 International License; see // http://creativecommons.org/licenses/by/4.0/ VkCommandPool(3) ================ Name ---- VkCommandPool - Opaque handle to a command pool object C Specification --------------- // refBegin VkCommandPool - Opaque handle to a command pool object Command pools are opaque objects that command buffer memory is allocated from, and which allow the implementation to amortize the cost of resource creation across multiple command buffers. Command pools are application-synchronized, meaning that a command pool mustnot: be used concurrently in multiple threads. That includes use via recording commands on any command buffers allocated from the pool, as well as operations that allocate, free, and reset command buffers or the pool itself. Command pools are represented by sname:VkCommandPool handles: include::../handles/VkCommandPool.txt[] Description ----------- // refEnd VkCommandPool See Also -------- slink:VkCommandBufferAllocateInfo, flink:vkCreateCommandPool, flink:vkDestroyCommandPool, flink:vkFreeCommandBuffers, flink:vkResetCommandPool Document Notes -------------- For more information, see the Vulkan Specification at URL https://www.khronos.org/registry/vulkan/specs/1.0/xhtml/vkspec.html#VkCommandPool This page is extracted from the Vulkan Specification. Fixes and changes should be made to the Specification,not directly. include::footer.txt[]