Skip to content

Simplify grouped gemm output allocations #4134

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jwfromm
Copy link
Contributor

@jwfromm jwfromm commented May 16, 2025

Summary: This very minor diff changes how output tensors in cutlass grouped gemm are allocated. Rather than treat them as a flat array, they now are allocated as standard matrices. This may help avoid an integer overflow error in the torch caching allocator.

Reviewed By: jiawenliu64

Differential Revision: D74852208

Summary: This very minor diff changes how output tensors in cutlass grouped gemm are allocated. Rather than treat them as a flat array, they now are allocated as standard matrices. This may help avoid an integer overflow error in the torch caching allocator.

Reviewed By: jiawenliu64

Differential Revision: D74852208
Copy link

netlify bot commented May 16, 2025

Deploy Preview for pytorch-fbgemm-docs ready!

Name Link
🔨 Latest commit aa04e38
🔍 Latest deploy log https://app.netlify.com/projects/pytorch-fbgemm-docs/deploys/68268853fa1bf5000876cb98
😎 Deploy Preview https://deploy-preview-4134--pytorch-fbgemm-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D74852208

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

Successfully merging this pull request may close these issues.

2 participants