Skip to content

Adds an extra command pool field in vkCommands#10203

Open
jorgeag-google wants to merge 1 commit into
google:mainfrom
jorgeag-google:async_cmndpool
Open

Adds an extra command pool field in vkCommands#10203
jorgeag-google wants to merge 1 commit into
google:mainfrom
jorgeag-google:async_cmndpool

Conversation

@jorgeag-google

Copy link
Copy Markdown
Contributor

This add an extra command pool to the vKCommands struct that will be used for the async work.

This is the first step to make the async commands in the VK backend really asynchronous.

@jorgeag-google jorgeag-google added the internal Issue/PR does not affect clients label Jul 13, 2026
VulkanCommands::VulkanCommands(VkDevice device, VkQueue queue, uint32_t queueFamilyIndex,
VkQueue protectedQueue, uint32_t protectedQueueFamilyIndex, VulkanContext const& context,
VkQueue protectedQueue, uint32_t protectedQueueFamilyIndex,
std::unique_ptr<CommandBufferPool> asyncPool, VulkanContext const& context,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this seems the wrong approach to me. Its strange to pass down one pool but then internally it creates one. Also what about the mSemaphoreManager.

In this case for the async, accessing the semaphore manager is that thread safe?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I changed the constructor. I am thinkinng if the semaphore manager needs to be thread safe. I know it is referenced in the command pool

This add an extra command pool to the vKCommands struct that will
be used for the async work.

This is the first step to make the async commands in the VK backend
really asynchronous.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal Issue/PR does not affect clients

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants