[ET-VK][Op Redesign][5/n] Merge StagingNode into ExecuteNode #2260
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):
We dispose of
StagingNode
in favor of functionsadd_staging_to_tensor_node()
andadd_tensor_to_staging_node()
, which each create anExecuteNode
. Hence, we fulfill our goal of makingExecuteNode
a final class. Theseadd_X_node()
are not anOpFunction
since staging is not an operator; its purpose is specific to starting and ending Vulkan execution.Note that we can't remove
encode_copy_to_vtensor()
as it's still used in ArithmeticPrepack. The prepack refactor is next.Differential Revision: D54445787