Open
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.
This is an experimental feature that adds a
bundle-dep-includesattribute to the build toml that enables the inclusion of cutlass headers in the build artifacts.This feature enables the deep-gemm kernel to be built, since the kernel does JIT compilation using the cutlass and cute library at runtime.
Initially I opted to vendor the dependencies in the kernel source but that adds hundreds of files that we already have available within the builder itself, this approach reuses the existing files and writes them into the build as shown below
└── torch29-cxx11-cu130-x86_64-linux ├── deep_gemm │ └── __init__.py ├── _deep_gemm_cuda_7f1079e_dirty.abi3.so ├── include │ ├── cute │ ├── cutlass │ └── deep_gemm ├── __init__.py ├── metadata.json ├── _ops.py └── utils ├── __init__.py └── math.py