[WIP] Experimental FlyDSL GEMM backend for TE PyTorch (BF16/FP16/FP32/FP8/MXFP8)#676
Draft
aris134 wants to merge 11 commits into
Draft
[WIP] Experimental FlyDSL GEMM backend for TE PyTorch (BF16/FP16/FP32/FP8/MXFP8)#676aris134 wants to merge 11 commits into
aris134 wants to merge 11 commits into
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
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
This PR introduces an experimental FlyDSL GEMM backend for the TransformerEngine PyTorch frontend, following PR #667
The initial implementation wires FlyDSL into the existing GEMM dispatch path and establishes the infrastructure needed to invoke FlyDSL kernels from TransformerEngine. FlyDSL is integrated as an optional dependency and is installed when the corresponding build option is enabled during TransformerEngine installation. At runtime, the backend is opt-in and selected via the NVTE_USE_FLYDSL=1 environment variable; otherwise, the existing TransformerEngine GEMM backend is used unchanged.
The FP16/BF16/FP8/MXFP8 GEMM paths have been integrated and verified against the existing TE implementation using a standalone end-to-end validation.
Remaining items