Optimize GPTQ-Pro kernels for Ampere decode and prefill - #11
Merged
Conversation
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
Introduces specialized Ampere execution paths while retaining the existing general-shape kernel as a correctness fallback.
CUDA runtime
M <= 4decode workloads.cp.asyncpipeline.int32 qweight, and scales.auto,gemv,ampere, andlegacymodes for validation and benchmarking.Memory and runtime
int32 qweightdirectly.post_init().group_size=-1handling in runtimeg_idxvalidation and kernel invocation.gptqmodel_gptq_pro_kernels_v2so stale cached/prebuilt binaries cannot be loaded with the new binding.GPTQMODEL_GPTQ_PRO_KERNELas an expert/debug dispatch override.Validation and measurement
Validation status
sm_80,sm_86,sm_87, and forward-compatible PTX.