Skip to content

mxfp8: use nvte_multi_tensor_quantize#588

Draft
matthiasdiener wants to merge 1 commit into
devfrom
mdiener/mxfp8-multi-tensor-quantize
Draft

mxfp8: use nvte_multi_tensor_quantize#588
matthiasdiener wants to merge 1 commit into
devfrom
mdiener/mxfp8-multi-tensor-quantize

Conversation

@matthiasdiener
Copy link
Copy Markdown
Contributor

@matthiasdiener matthiasdiener commented May 15, 2026

Description

Please include a brief summary of the changes, relevant motivation and context.

Fixes # (issue)

Type of change

  • Documentation change (change only to the documentation, either a fix or a new content)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Infra/Build change
  • Code refactoring

Changes

Please list the changes introduced in this PR:

  • Change A
  • Change B

Checklist:

  • I have read and followed the contributing guidelines
  • The functionality is complete
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

@matthiasdiener matthiasdiener requested a review from alextmagro May 15, 2026 19:47
@matthiasdiener matthiasdiener self-assigned this May 15, 2026
@matthiasdiener matthiasdiener added the ci-level 1 CI test level 1 label May 15, 2026
@alextmagro
Copy link
Copy Markdown
Contributor

Code itself looks good -- Can you post some performance info on the E2E differences between this multi quantize path and the old path? Also, which tests are hitting this logic?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-level 1 CI test level 1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants