Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

There is no need in separation for transfer queue #45

Open
tomilov opened this issue Dec 21, 2019 · 0 comments
Open

There is no need in separation for transfer queue #45

tomilov opened this issue Dec 21, 2019 · 0 comments

Comments

@tomilov
Copy link

tomilov commented Dec 21, 2019

You wrote:

// TODO: separate transfer queue (if not supported by compute queue) including buffer ownership transfer

but there is a note:

Note
All commands that are allowed on a queue that supports transfer operations are also allowed on a queue that supports either graphics or compute operations. Thus, if the capabilities of a queue family include VK_QUEUE_GRAPHICS_BIT or VK_QUEUE_COMPUTE_BIT, then reporting the VK_QUEUE_TRANSFER_BIT capability separately for that queue family is optional.

So in most cases there is no need to separate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant