-
Notifications
You must be signed in to change notification settings - Fork 335
Add Queue/writeBuffer method #749
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
Conversation
Thanks @kainino0x ! Your notes are addressed now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One comment, otherwise looks great
Thanks @austinEng ! I agree, although there are many other places where we could throw. But this is a start :) |
Nothing is missing, as far as I know. Just don't want to self-merge, and giving more chance for folks outside of Google-Mozilla to look. Please feel free to merge, especially since it's blocking you. |
If anyone else still wants to review, please do so and we can follow up. |
653: Implement Queue::write_buffer r=nobody a=kvark Implements gpuweb/gpuweb#749 TODO: - [x] handle a case where the buffer is dropped while there is a pending write. Edit: we bump the submission index on the buffer, so it will be kept alive. - [x] properly free the temporary buffer and memory - [x] properly destroy the pending command buffer on device drop - [x] tweak the linear allocator settings - bumped to 16 megs - [x] provide a patch to wgpu-rs and verify it works on the examples - gfx-rs/wgpu-rs#307 - [x] provide a patch to wgpu-native - gfx-rs/wgpu-native#25 - [x] check/fix the trace/replay support Co-authored-by: Dzmitry Malyshau <[email protected]>
* Add Queue/writeBuffer method * Address Kai's comments * Throw under some conditions in writeBuffer
* Add Queue/writeBuffer method * Address Kai's comments * Throw under some conditions in writeBuffer
This is the
writeBuffer
proposal moved out of #509Preview | Diff