Skip to content

[ET-VK][BE] Move all ops to use DynamicDispatchNode #13158

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

Merged
merged 1 commit into from
Aug 7, 2025

Conversation

SS-JIA
Copy link
Contributor

@SS-JIA SS-JIA commented Aug 6, 2025

Stack from ghstack (oldest at bottom):

Changes

Update (almost) all operators use DynamicDispatchNode instead of DispatchNode.

Context

DynamicDispatchNode was introduced in order to provide a way for operators to adjust

  1. Which compute shader to dispatch
  2. What global work group size to use
  3. What local work group size to use

Based 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

## Changes

Update (almost) all operators use `DynamicDispatchNode` instead of `DispatchNode`.


## Context

`DynamicDispatchNode` was introduced in order to provide a way for operators to adjust

1. Which compute shader to dispatch
2. What global work group size to use
3. What local work group size to use

Based 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](https://our.internmc.facebook.com/intern/diff/D79564595/)

[ghstack-poisoned]
Copy link

pytorch-bot bot commented Aug 6, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/13158

Note: Links to docs will display an error until the docs builds have been completed.

❌ 1 New Failure, 1 Unrelated Failure

As of commit 4fea607 with merge base 6bc312a (image):

NEW FAILURE - The following job has failed:

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Aug 6, 2025
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D79564595

@trivedivivek trivedivivek added the release notes: vulkan Changes to the Vulkan backend delegate label Aug 6, 2025
@facebook-github-bot facebook-github-bot merged commit 4c921b4 into gh/SS-JIA/269/base Aug 7, 2025
102 of 107 checks passed
@facebook-github-bot facebook-github-bot deleted the gh/SS-JIA/269/head branch August 7, 2025 01:02
kirklandsign pushed a commit that referenced this pull request Aug 7, 2025
## Context

As title. #13158 and
#13159 landed in Meta internal
repo as diffs but there was a problem creating a merge PR. This PR
manually adds the changes from those PRs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported release notes: vulkan Changes to the Vulkan backend delegate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants