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

Fork CUDA and ROCm guides into separate pages. #15196

Merged
merged 1 commit into from
Oct 17, 2023

Conversation

ScottTodd
Copy link
Member

Fixes #15115

These pages are very similar, but both stacks have undergone enough development recently that they can now stand on their own. This PR primarily forks the pages, but it also does some minor cleanup (fixing dead links, adjusting formatting).

Current page https://www.iree.dev/guides/deployment-configurations/gpu-cuda-rocm/
Preview of this PR - CUDA https://scotttodd.github.io/iree/guides/deployment-configurations/gpu-cuda
Preview of this PR - ROCm https://scotttodd.github.io/iree/guides/deployment-configurations/gpu-rocm

@ScottTodd ScottTodd added documentation ✏️ Improvements or additions to documentation hal/cuda Runtime CUDA HAL backend hal/rocm labels Oct 16, 2023
Comment on lines +100 to +112
Using MobileNet v2 as an example, you can download the SavedModel with trained
weights from
[TensorFlow Hub](https://tfhub.dev/google/tf2-preview/mobilenet_v2/classification)
and convert it using IREE's
[TensorFlow importer](../ml-frameworks/tensorflow.md). Then run one of the
following commands to compile:

```shell hl_lines="2-3"
iree-compile \
--iree-hal-target-backends=cuda \
--iree-hal-cuda-llvm-target-arch=<...> \
mobilenet_iree_input.mlir -o mobilenet_cuda.vmfb
```
Copy link
Member Author

Choose a reason for hiding this comment

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

These TF sections should be replaced with something more generic. Future work...

@raikonenfnu
Copy link
Collaborator

Fixes #15115

These pages are very similar, but both stacks have undergone enough development recently that they can now stand on their own. This PR primarily forks the pages, but it also does some minor cleanup (fixing dead links, adjusting formatting).

Current page https://www.iree.dev/guides/deployment-configurations/gpu-cuda-rocm/
Preview of this PR - CUDA https://scotttodd.github.io/iree/guides/deployment-configurations/gpu-cuda
Preview of this PR - ROCm https://scotttodd.github.io/iree/guides/deployment-configurations/gpu-rocm

Tbh, both pages still looks quite similar to me for now haha, I do think it's good to start splitting them up for better legibility and UI/UX. :)

Just curious, are there any other reasons you started splitting the page up?

@ScottTodd
Copy link
Member Author

Fixes #15115
These pages are very similar, but both stacks have undergone enough development recently that they can now stand on their own. This PR primarily forks the pages, but it also does some minor cleanup (fixing dead links, adjusting formatting).
Current page https://www.iree.dev/guides/deployment-configurations/gpu-cuda-rocm/
Preview of this PR - CUDA https://scotttodd.github.io/iree/guides/deployment-configurations/gpu-cuda
Preview of this PR - ROCm https://scotttodd.github.io/iree/guides/deployment-configurations/gpu-rocm

Tbh, both pages still looks quite similar to me for now haha, I do think it's good to start splitting them up for better legibility and UI/UX. :)

Just curious, are there any other reasons you started splitting the page up?

Yeah, I could go either way here. On one end, we could fold all of the GPU pages (Vulkan, CUDA, ROCm, Metal) into a single page, and on the other (this PR), we could split them into separate pages. We're currently somewhere in the middle, since CUDA and ROCm were both at very similar stages of (early) development.

The main reason I want separate pages is for clear messaging to users that each backend can stand on its own and can provide differentiating features.

  • Vulkan: interop with graphics APIs, portability to platforms like Android
  • CUDA: multi-GPU setups (collectives), plugins/comparisons/integrations with other NVIDIA libraries
  • ROCm: AMD GPU support with specialization not possible via Vulkan
  • Metal: direct support on Apple platforms, without going through compatibility layers (MoltenVK)

The implementations are (by design) quite similar in IREE, and some users may appreciate side by side comparisons, but I expect that many users will already know what hardware/APIs they are using and would rather see documentation specialized for that.

@raikonenfnu
Copy link
Collaborator

SGTM!

@ScottTodd ScottTodd merged commit 87a1cc6 into iree-org:main Oct 17, 2023
53 checks passed
@ScottTodd ScottTodd deleted the docs-rocm-split branch October 17, 2023 21:55
ramiro050 pushed a commit to ramiro050/iree that referenced this pull request Dec 19, 2023
Fixes iree-org#15115

These pages are very similar, but both stacks have undergone enough
development recently that they can now stand on their own. This PR
primarily forks the pages, but it also does some minor cleanup (fixing
dead links, adjusting formatting).

|  | |
|--------|--------|
| Current page |
https://www.iree.dev/guides/deployment-configurations/gpu-cuda-rocm/ |
| Preview of this PR - CUDA |
https://scotttodd.github.io/iree/guides/deployment-configurations/gpu-cuda
|
| Preview of this PR - ROCm |
https://scotttodd.github.io/iree/guides/deployment-configurations/gpu-rocm
|
@ScottTodd ScottTodd added the hal/hip Runtime HIP HAL backend label Jul 9, 2024
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 hal/cuda Runtime CUDA HAL backend hal/hip Runtime HIP HAL backend
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Split CUDA/ROCm website page into two
2 participants