-
Notifications
You must be signed in to change notification settings - Fork 363
float8 inference: fix bmm semantics #3296
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
Merged
+21
−14
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -422,24 +422,25 @@ def _(func, types, args, kwargs): | |
| a_scale = input_tensor.scale | ||
|
|
||
| b_data = weight_tensor.qdata | ||
| b_scale = weight_tensor.scale.squeeze(-1) | ||
| assert b_data.is_contiguous(), "weight for bmm must be contiguous" | ||
| b_scale = weight_tensor.scale | ||
|
|
||
| assert ( | ||
| all(x == 1 for x in weight_tensor.block_size[:-1]) | ||
| and weight_tensor.block_size[-1] == weight_tensor.shape[-1] | ||
| weight_tensor.block_size[0] == 1 | ||
| and weight_tensor.block_size[1] == weight_tensor.shape[1] | ||
| and weight_tensor.block_size[2] == 1 | ||
| ), "bmm only works for per row weight quantization" | ||
| assert ( | ||
| all(x == 1 for x in input_tensor.block_size[:-1]) | ||
| and input_tensor.block_size[-1] == input_tensor.shape[-1] | ||
| ), "bmm only works for per row activation quantization" | ||
|
|
||
| orig_out_features = b_data.shape[-2] | ||
| orig_out_features = b_data.shape[-1] | ||
|
|
||
| res = torch.ops.fbgemm.f8f8bf16_rowwise_batched( | ||
| a_data, | ||
| b_data, | ||
| b_data.transpose(-2, -1), | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. will performance be a concern?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. transpose is just metadata, no impact on performance |
||
| a_scale, | ||
| b_scale.transpose(-2, -1), | ||
| b_scale, | ||
| ) | ||
| res = res.reshape(*orig_act_size[:-1], orig_out_features) | ||
|
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
this was from llama-models I think: https://github.com/meta-llama/llama-models/blob/0e0b8c519242d5833d8c11bffc1232b77ad7f301/models/llama4/quantization/loader.py#L142, although not as important now
but I guess the important thing is how do we implement it in a way that it can be used by different implementations, would current fp8 bmm implementation work for different ways people use bmm?
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.
this is overriding
torch.bmm, so we definitely should match the semantics oftorch.bmmin terms of input shapes. It doesn't make sense to do a bmm with shapes that aren't (B, M, K) and (B, K, N). If that breaks llama-models, then they should fix it to match bmm semantics.