[Feature]Cutlass (re) integration #1393
Draft
Conversation
This file contains 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.
Hi @TimDettmers , @Titus-von-Koeller & @matthewdouglas ,
This is part of our initial discussion to (re) integrate and try out cutlass integration support for gemm device kernel.
Currently this is a WIP as I am testing out standalone cutlass gemms (without cute) and would incorporate cute if required for performance. Yes this took some time as was caught up in some other work , but plan to actively add/integrate this feature to cuda backend. In longer run , we plan to integrate this in sycl backend as well.
cc @mehdi-goli for review and feedbacks .