Skip to content
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

Does cumm support a dynamic mode to decide to use cutlass or its own gemm based on input shapes? #14

Open
umiswing opened this issue Oct 15, 2022 · 1 comment

Comments

@umiswing
Copy link
Contributor

umiswing commented Oct 15, 2022

Hello! I'm interested in cumm and find it's very fast. I read cumm's code and found it seems that cumm provides a gemm implement from scratch while also providing a cutlass mode. And cumm will use its own gemm by default. I do some experiments, and I find that for some shapes, the cutlass will get faster, and for others, cumm's gemm will be faster. Does cumm support a dynamic mode to decide to use cutlass or its own gemm based on the input shapes?

@umiswing umiswing changed the title Does cumm support a dynamic mode to decide use cutlass or its own gemm? Does cumm support a dynamic mode to decide to use cutlass or its own gemm based on input shapes? Oct 15, 2022
@FindDefinition
Copy link
Owner

currently not, but looks like a good feature to use new cutlass feature quickly instead of re-implement them. I will consider this feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants