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

Decouple device and queue IDs #6070

Merged
merged 1 commit into from
Aug 5, 2024

Conversation

teoxoy
Copy link
Member

@teoxoy teoxoy commented Aug 2, 2024

Connections
Fixes #5092.

Description
Devices and queues can have different lifetimes, we shouldn't assume that their IDs match.
I had to slightly refactor the WaitIdleError::WrongSubmissionIndex error because we don't store the queue ID internally.

Testing
Added a test.

@teoxoy teoxoy requested a review from a team as a code owner August 2, 2024 11:58
Devices and queues can have different lifetimes, we shouldn't assume that their IDs match.
@nical
Copy link
Contributor

nical commented Aug 5, 2024

The gecko side will need to be adapted to this.

@teoxoy teoxoy merged commit 8c7c5c4 into gfx-rs:trunk Aug 5, 2024
25 checks passed
@teoxoy teoxoy deleted the decouple_device_and_queue_IDs branch August 5, 2024 13:46
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

Successfully merging this pull request may close these issues.

Queue[Id(1,2,d3d12)] does not exist internal panic during Queue::write_buffer() on DX12 backend
2 participants