-
Notifications
You must be signed in to change notification settings - Fork 6k
[Impeller] add async command submission for blit pass. #48040
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why is this change unconditional? Do we always want to do this? I guess I'm confused here - is synchronous submission being removed after this lands?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ^ What about this question? LGTM otherwise.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ahh yes, we always want to do this. no, its not being removed because it is still useful for workloads that happen outside of the frame workload (like image upload/mipmaps). There is also no way to create multiple render passes from a single cmd buffer and async submit them, which we don't need to do right now, but only the old API supports that technically. |
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.
Just based off of reading this, maybe it should be
EncodeAndSubmitCommandsAsync.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.
Yeah that is a good suggestion, i will do that (not today, but when I update this tomrrow) 😄
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.
Done