-
Notifications
You must be signed in to change notification settings - Fork 288
Improve GemLite Integration #2096
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
Summary: att Test Plan: TODO Reviewers: Subscribers: Tasks: Tags:
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/ao/2096
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 0e65350 with merge base 11472c9 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
torchao/testing/utils.py
Outdated
@@ -91,12 +91,30 @@ def wrapper(*args, **kwargs): | |||
|
|||
|
|||
def skip_if_no_cuda(): | |||
import unittest | |||
import pytest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we might have to use unittest to make CI happy I think
Tasks
get_plain()
via Triton unpacking instead of matmul with the identity matrix -> slicing should be faster..to()
to allow loading models in transformers.from_plain
/get_plain
for vllm weight loader compatibllity.Note: Slicing still performs unpacking -> packing. If we can restrict the step to be
self._layout.packing_bitwidth // self._layout.bit_width
we can avoid this and slice directly the packed data.Test