[gfx1100] Enable RDNA3 in arch allow-list + Triton GEMM A8W8 tuning config - #4778
Open
okone1995 wants to merge 2 commits into
Open
[gfx1100] Enable RDNA3 in arch allow-list + Triton GEMM A8W8 tuning config#4778okone1995 wants to merge 2 commits into
okone1995 wants to merge 2 commits into
Conversation
Contributor
🏷️ CI GuideRuns automatically on every PR:
Extended tests (opt-in via labels):
|
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.
Summary
Follow-up to #4604 with the working reference implementation discussed there.
vLLM's AITER integration gate (
is_aiter_found_and_supported()) covers CDNA3+ and RDNA4, but never gfx1100 (RDNA3) — even though AITER's README lists W7900 / gfx1100 as Experimental, andconfigs/gemm/already ships tuned A8W8 configs for gfx1151/1201/1250 but not gfx1100. This PR contributes the aiter-side half of the port (vLLM-side gate change to be submitted separately, tracked in vllm-project/vllm#51136).Changes
csrc/cpp_itfs/utils.py— addgfx1100to theallowed_archslist invalidate_and_update_archs(). The stale list only covered gfx9x + gfx1151 and rejectedGPU_ARCHS=gfx1100at compile time.aiter/ops/triton/configs/gemm/gfx1100-GEMM-A8W8.json— new M-band tuning config for the Triton WMMA path (none existed for RDNA3), same M_LEQ_x / M_GEQ_y / any schema as sibling configs:BLOCK_SIZE_M=16, N=128, K=128, warps=4, stages=3-> 0.071 ms/GEMMBLOCK_SIZE_M=64, N=256, warps=8-> 4.4 ms @ M=2048Note: AITER's CK-based
gemm_a8w8_CKkernels are XDL-only and compile-fail on RDNA3, so gfx1100 routes to the pure-Tritongemm_a8w8kernel.Validation (Radeon PRO W7900 48GB, ROCm 7.2.4, vLLM 0.26.0, Aug 3 2026)
Model: Qwen3.6-27B Quark W8A8-INT8, multimodal OCR workload (insurance claim agent, ~4k ctx):
Functional parity, not speedup — reported honestly. On this workload the decode bottleneck is 140+ serialized per-layer kernels on RDNA3 WMMA, not a single GEMM. The value here is enabling the native AITER stack (quantized GEMM + GDN decode + conv1d + sampler) on RDNA3 at all; per-shape tuning is left as future work.
Enable with:
VLLM_ROCM_USE_AITER=1 GPU_ARCHS=gfx1100; vLLM log confirmsSelected AiterInt8ScaledMMLinearKernel.Only gfx1100 (W7900) is tested; other RDNA3 variants (gfx1101/1102/1103) are expected to work but untested — happy to extend the allow-list if maintainers prefer.
Related