-
Notifications
You must be signed in to change notification settings - Fork 916
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JNI Bindings to fetch CUDA compute capability versions. #10568
JNI Bindings to fetch CUDA compute capability versions. #10568
Conversation
70da1cd
to
6284685
Compare
Signed-off-by: MithunR <[email protected]>
6284685
to
dfd9975
Compare
Codecov Report
@@ Coverage Diff @@
## branch-22.04 #10568 +/- ##
================================================
+ Coverage 86.15% 86.17% +0.01%
================================================
Files 141 141
Lines 22510 22510
================================================
+ Hits 19394 19397 +3
+ Misses 3116 3113 -3
Continue to review full report at Codecov.
|
1. Moved implementation inline. Removed util function. 2. Renamed to getComputeCapabilityM{aj,in}or.
I'm running the ( |
Is this coming to the (frozen) 22.04? Or it was a mistake? |
We're working on addressing NVIDIA/spark-rapids/issues/4980 in the 22.04 timeframe. |
Tested on Pascal and Turing. Verified that this satisfies the intent of NVIDIA/spark-rapids/pull/5122. |
Updated the description for more context. I'm not sure I agree that the whole story needs to be in the commit message (rather than, say, in a comment), but I'll put it there for convenience. |
This commit introduces JNI bindings to retrieve the major and minor CUDA compute capability versions for the current CUDA device.
This feature enables introspection from
spark-rapids
to detect the GPU architecture, for model-specific behaviour.This is required from NVIDIA/spark-rapids/pull/5122, to work around the erroneous behaviour of JNI
fixed_width_convert_to_rows()
on Pascal GPUs (#10569), (which in turn produces failures like NVIDIA/spark-rapids/issues/4980).