Add full mlx blockwise support#2233
Open
jessegrabowski wants to merge 2 commits into
Open
Conversation
ricardoV94
reviewed
Jun 16, 2026
ricardoV94
approved these changes
Jun 20, 2026
Member
|
failing test |
da138df to
e95b8c7
Compare
e95b8c7 to
d53a158
Compare
d53a158 to
3f11bb2
Compare
Member
|
that ci looks like fun |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
MLX blockwise operations fail in non-trivial cases because our implementation isn't a full vectorize, it's just a single naive application of
mlx.vmap. We need to align and broadcast all input shapes, then applyvmaponce per non-core dimension. This is whatjnp.vectorizedoes under the hood. I just went ahead and re-implementedjnp.vectorizein MLX, giving us full vectorize support.Closes #2092 , and also address additional unreported cases (e.g. when data has batch dim).