-
Notifications
You must be signed in to change notification settings - Fork 338
Add dynamic quantization support to gemlite layout #2327
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
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/ao/2327
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (2 Unrelated Failures)As of commit a94c9cf with merge base dd22777 ( BROKEN TRUNK - The following jobs failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
I think by "static" you meant weight only? |
Signed-off-by: mobicham <[email protected]>
Anything else to have this merged? Thank you! |
we can merge now, the test failures does not look related |
* fix get_plain() with FMA mode * update * fix in_features/out_feature meta-data mismatch * update gemlite slice test * add packing_bitwidth support * add packing_bitwidth support and cleanup * update default gemlite layout * cleanup * fix symmetric use-case and relax _same_meta_data * _copy() meta data * fix (4,) in autoquant * Add dynamic mode in gemlite layout * mode explanation Signed-off-by: mobicham <[email protected]> * use weights_only instead of static --------- Signed-off-by: mobicham <[email protected]>
This PR adds dynamic quantization support to the GemLite layout. The new config param is
mode
:mode="weight_only"
- no activation quantization (default).mode="dynamic"
- uses int8 dynamic quantization for A8W8 and fp8 for A8Wn.