Repository navigation
Conversation
Assisted-by: Codex
|
Hi @mmalpe-nv, thanks for your contribution! Per our contribution guidelines, the automated PR checker found the following issue(s) that need your attention:
Please note that maintainers reserve the right to make final decisions on PRs. If you believe there is a mistake, please comment below. |
This branch has not been deployed
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
1 participant
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.
Overview
The change makes automatic cuBLAS precision selection depending on the NVIDIA GPU. Eligible quantized operations retain FP16 inputs and accumulation on GeForce, while supported professional GPUs and Spark prefer BF16 inputs with FP32 accumulation.
It adds GPU classification using NVML brand information and Spark’s compute capability, while preserving existing operation-specific precision requirements and manual overrides. The aim is to use each GPU’s capabilities without imposing the FP32-accumulation throughput penalty on GeForce.
Additional information
Requirements