Skip to content

Conversation

@msimberg
Copy link
Collaborator

Adds a "Communication Libraries" subtree next to scientific applications and others under "Software". I've populated the Cray MPICH page with information on using GPU-aware MPI and the known issues page from the old knowledge base. Other pages (OpenMPI, NCCL, RCCL, and libfabric) are mostly stubs at the moment.

@msimberg msimberg requested review from RMeli and bcumming March 12, 2025 16:07
@github-actions
Copy link

preview available: https://docs.tds.cscs.ch/40

This means that the required GTL library was not linked to the application.
In supported uenvs, GPU support is enabled by default.
If you believe a uenv should have GPU support but you are getting the above error, feel free to [get in touch with us][ref-get-in-touch] to understand whether there is an issue with the uenv or something else in your environment.
If you are using Cray modules you must load the corresponding accelerator module, e.g. `craype-accel-nvidia90`, before compiling your application.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
If you are using Cray modules you must load the corresponding accelerator module, e.g. `craype-accel-nvidia90`, before compiling your application.
If you are using Cray modules you must load the corresponding accelerator module, e.g. `craype-accel-nvidia90`, before compiling your application.

Worth mentioning something about our support for Cray modules? Or maybe just remove this?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yeah, I wasn't sure. I've tried to mention them as little as possible, but we do still get tickets every now and then about this and in most cases when GTL isn't linked it's when the user is using modules, not uenv.

I guess it would make sense to have a Software -> Cray Modules section, even if it's just to say that their use is discouraged? Then we could link to that. And any potential containerized use of Cray modules would also be described there.

@bcumming any long term opinions on how to deal with Cray modules in the docs?

@github-actions
Copy link

preview available: https://docs.tds.cscs.ch/40

@github-actions
Copy link

preview available: https://docs.tds.cscs.ch/40

@github-actions
Copy link

preview available: https://docs.tds.cscs.ch/40

@github-actions
Copy link

preview available: https://docs.tds.cscs.ch/40

@github-actions
Copy link

preview available: https://docs.tds.cscs.ch/40

@github-actions
Copy link

preview available: https://docs.tds.cscs.ch/40

@github-actions
Copy link

preview available: https://docs.tds.cscs.ch/40

@bcumming bcumming merged commit a83650d into main Mar 14, 2025
1 check passed
@bcumming bcumming deleted the comm-libs branch March 14, 2025 13:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants