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

Add INT8 support to fbgemm qcomm lib #1337

Closed
wants to merge 1 commit into from

Conversation

yusuo
Copy link

@yusuo yusuo commented Sep 19, 2022

Summary:
Add INT8 codec to fbgemm library. Also defined a context class to pass the row_dim and row_dim_quant parameters during coding and encoding.

For INT8, the output size is decided by row dim, which is needed by high level collective communication modules. To that purpose, this diff adds a new calc_quantized_size function and implement it based on the INT8 codec logic.

Differential Revision: D39473386

@netlify
Copy link

netlify bot commented Sep 19, 2022

Deploy Preview for eclectic-stroopwafel-199537 canceled.

Name Link
🔨 Latest commit 29a8f95
🔍 Latest deploy log https://app.netlify.com/sites/eclectic-stroopwafel-199537/deploys/6328eec0f8d7fb000817b489

@facebook-github-bot
Copy link
Contributor

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

Summary:
Pull Request resolved: pytorch#1337

Add INT8 codec to fbgemm library. Also defined a context class to pass the row_dim and row_dim_quant parameters during coding and encoding.

For INT8, the output size is decided by row dim, which is needed by high level collective communication modules. To that purpose, this diff adds a new calc_quantized_size function and implement it based on the INT8 codec logic.

Differential Revision: D39473386

fbshipit-source-id: 445060348bbda368c8c5a8df1bd60c60a0be12c3
@facebook-github-bot
Copy link
Contributor

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

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