vkCreateCommandPool - Create a new command pool object

Parameters

• device is the logical device that creates the command pool.

• pCreateInfo is a pointer to a CommandPoolCreateInfo structure specifying the state of the command pool object.
• pAllocator controls host memory allocation as described in the Memory Allocation chapter.
• pCommandPool is a pointer to a CommandPool handle in which the created pool is returned.

Valid Usage

• pCreateInfo->queueFamilyIndex must be the index of a queue family available in the logical device device

Valid Usage (Implicit)

• device must be a valid Device handle

• pCreateInfo must be a valid pointer to a valid CommandPoolCreateInfo structure
• If pAllocator is not NULL, pAllocator must be a valid pointer to a valid AllocationCallbacks structure
• pCommandPool must be a valid pointer to a CommandPool handle

Return Codes

Success

• SUCCESS

Failure

• ERROR_OUT_OF_HOST_MEMORY
• ERROR_OUT_OF_DEVICE_MEMORY

See Also

AllocationCallbacks, CommandPool, CommandPoolCreateInfo, Device

A convenience wrapper to make a compatible pair of calls to createCommandPool and destroyCommandPool

To ensure that destroyCommandPool is always called: pass bracket (or the allocate function from your favourite resource management library) as the first argument. To just extract the pair pass '(,)' as the first argument.

vkDestroyCommandPool - Destroy a command pool object

Parameters

• device is the logical device that destroys the command pool.

• commandPool is the handle of the command pool to destroy.
• pAllocator controls host memory allocation as described in the Memory Allocation chapter.

Description

When a pool is destroyed, all command buffers allocated from the pool are freed.

Any primary command buffer allocated from another CommandPool that is in the recording or executable state and has a secondary command buffer allocated from commandPool recorded into it, becomes invalid.

Valid Usage

• All CommandBuffer objects allocated from commandPool must not be in the pending state

• If AllocationCallbacks were provided when commandPool was created, a compatible set of callbacks must be provided here
• If no AllocationCallbacks were provided when commandPool was created, pAllocator must be NULL

Valid Usage (Implicit)

• device must be a valid Device handle

• If commandPool is not NULL_HANDLE, commandPool must be a valid CommandPool handle
• If pAllocator is not NULL, pAllocator must be a valid pointer to a valid AllocationCallbacks structure
• If commandPool is a valid handle, it must have been created, allocated, or retrieved from device

Host Synchronization

• Host access to commandPool must be externally synchronized

See Also

AllocationCallbacks, CommandPool, Device

vkResetCommandPool - Reset a command pool

Parameters

• device is the logical device that owns the command pool.

• commandPool is the command pool to reset.
• flags is a bitmask of CommandPoolResetFlagBits controlling the reset operation.

Description

Resetting a command pool recycles all of the resources from all of the command buffers allocated from the command pool back to the command pool. All command buffers that have been allocated from the command pool are put in the initial state.

Any primary command buffer allocated from another CommandPool that is in the recording or executable state and has a secondary command buffer allocated from commandPool recorded into it, becomes invalid.

Valid Usage

• All CommandBuffer objects allocated from commandPool must not be in the pending state

Valid Usage (Implicit)

• device must be a valid Device handle

• commandPool must be a valid CommandPool handle
• flags must be a valid combination of CommandPoolResetFlagBits values
• commandPool must have been created, allocated, or retrieved from device

Host Synchronization

• Host access to commandPool must be externally synchronized

Return Codes

Success

• SUCCESS

Failure

• ERROR_OUT_OF_HOST_MEMORY
• ERROR_OUT_OF_DEVICE_MEMORY

See Also

CommandPool, CommandPoolResetFlags, Device

VkCommandPoolCreateInfo - Structure specifying parameters of a newly created command pool

Valid Usage

• If the protected memory feature is not enabled, the COMMAND_POOL_CREATE_PROTECTED_BIT bit of flags must not be set

Valid Usage (Implicit)

• sType must be STRUCTURE_TYPE_COMMAND_POOL_CREATE_INFO

• pNext must be NULL
• flags must be a valid combination of CommandPoolCreateFlagBits values

See Also

CommandPoolCreateFlags, StructureType, createCommandPool