Skip to content
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

Branch 21.10 FAQ update forward compatibility, update Spark and CUDA versions #3308

Merged
merged 4 commits into from
Aug 26, 2021

Conversation

sameerz
Copy link
Collaborator

@sameerz sameerz commented Aug 25, 2021

Updated FAQ to correct support for forward compatibility. Updated Spark and CUDA versions as of today, will update again when Spark 3.2 is supported.

@sameerz sameerz added the documentation Improvements or additions to documentation label Aug 25, 2021
@sameerz sameerz added this to the Aug 16 - Aug 27 milestone Aug 25, 2021
@sameerz sameerz requested review from jlowe and viadea August 25, 2021 22:04
@sameerz sameerz self-assigned this Aug 25, 2021

### What hardware is supported?

The plugin is tested and supported on V100, T4, A10, A30 and A100 datacenter GPUs. It is possible
to run the plugin on GeForce desktop hardware with Volta or better architectures. GeForce hardware
does not support [CUDA enhanced
compatibility](https://docs.nvidia.com/deploy/cuda-compatibility/index.html#enhanced-compat-minor-releases),
does not support [CUDA forward
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

docs/FAQ.md Outdated Show resolved Hide resolved
docs/FAQ.md Outdated Show resolved Hide resolved
@@ -30,15 +30,15 @@ to set up testing and validation on their distributions.

### What CUDA versions are supported?

CUDA 11.0 and 11.2 are currently supported. Please look [here](download.md) for download links for
the latest release.
CUDA 11.x is currently supported. Please look [here](download.md) for download links for the latest
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was going to ask if we should retain the old phrasing here, for fear of 11.1. But it appears the CUDF docs mention 11.x.

👍

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The cudf team seems to fix any compiling issue for CUDA 11.X. If there is any problem, just report them. I just did once for CUDA 11.0 which is now fixed (rapidsai/cudf#9028).

mythrocks
mythrocks previously approved these changes Aug 25, 2021
Copy link
Collaborator

@mythrocks mythrocks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Fix compatibility spelling

Co-authored-by: Jason Lowe <[email protected]>
Add a comma

Co-authored-by: MithunR <[email protected]>
@jlowe
Copy link
Member

jlowe commented Aug 25, 2021

build

@@ -30,15 +30,15 @@ to set up testing and validation on their distributions.

### What CUDA versions are supported?

CUDA 11.0 and 11.2 are currently supported. Please look [here](download.md) for download links for
the latest release.
CUDA 11.x is currently supported. Please look [here](download.md) for download links for the latest
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
CUDA 11.x is currently supported. Please look [here](download.md) for download links for the latest
CUDA 11.x is currently supported. Please look [here](download.md) for download links for the latest

@@ -30,15 +30,15 @@ to set up testing and validation on their distributions.

### What CUDA versions are supported?

CUDA 11.0 and 11.2 are currently supported. Please look [here](download.md) for download links for
the latest release.
CUDA 11.x is currently supported. Please look [here](download.md) for download links for the latest
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The cudf team seems to fix any compiling issue for CUDA 11.X. If there is any problem, just report them. I just did once for CUDA 11.0 which is now fixed (rapidsai/cudf#9028).

Comment on lines 38 to 39
The plugin is tested and supported on V100, T4, A10, A30 and A100 datacenter GPUs. It is possible
to run the plugin on GeForce desktop hardware with Volta or better architectures. GeForce hardware
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The plugin is tested and supported on V100, T4, A10, A30 and A100 datacenter GPUs. It is possible
to run the plugin on GeForce desktop hardware with Volta or better architectures. GeForce hardware
The plugin is tested and supported on V100, T4, A10, A30 and A100 datacenter GPUs. It is possible
to run the plugin on GeForce desktop hardware with Volta or better architectures. GeForce hardware

@sameerz
Copy link
Collaborator Author

sameerz commented Aug 26, 2021

We will work on the spaces issue that @ttnghia brought up in a future PR.

@sameerz sameerz merged commit 91b3a68 into NVIDIA:branch-21.10 Aug 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants