You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Refactor: Decouple GMM kernel backend dispatch from quantization logic in MoE sparse_matmul #3646
Kernel backend dispatch — choosing between megablox Pallas, tokamax Pallas, or jax.lax.ragged_dot
This leads to confusing control flow where mblx.gmm() acts as both a "quantization-aware GMM wrapper" and a "backend router" via the use_tokamax_backend flag. The megablox module shouldn't need to know about tokamax at all.
Activity
gobbleturk commentedon Apr 14, 2026
These are great ideas, we will work on improving/refactoring, thank you! I agree with your desired flow