Resolve wgrad grouped gemm relocation issue in fbgemm #4915
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…resubmit) Differential Revision: D83001505
Differential Revision: D82700396
Differential Revision: D82700455
Summary: X-link: facebookresearch/FBGEMM#1939 This Diff resolves wgrad cutlass grouped gemm relocation issue in fbgemm in short-term For long term, we might need to refactor fbgemm genai quantize ops by spliting targets (or other more elegant solution) to reduce fbgemm binary sizes for internal buck build for xfn usage to avoid issue such as T238469849 Differential Revision: D83020887
|
@jiawenliu64 has exported this pull request. If you are a Meta employee, you can view the originating diff in D83020887. |
✅ Deploy Preview for pytorch-fbgemm-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary:
X-link: https://github.com/facebookresearch/FBGEMM/pull/1939
This Diff resolves wgrad cutlass grouped gemm relocation issue in fbgemm in short-term
For long term, we might need to refactor fbgemm genai quantize ops by spliting targets (or other more elegant solution) to reduce fbgemm binary sizes for internal buck build for xfn usage to avoid issue such as T238469849
Differential Revision: D83020887