[ET-VK][BE] Move all ops to use DynamicDispatchNode
#13158
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Stack from ghstack (oldest at bottom):
DynamicDispatchNode
#13159DynamicDispatchNode
#13158get_tensor()
API protected #13157vTensorPtr
andget_tensor
#13156Changes
Update (almost) all operators use
DynamicDispatchNode
instead ofDispatchNode
.Context
DynamicDispatchNode
was introduced in order to provide a way for operators to adjustBased on the current input and output shapes. This is useful for making sure that the most optimal compute shader is used for the current tensor sizes, and minimizing the number of inactive shader invocations.
Differential Revision: D79564595