-
Notifications
You must be signed in to change notification settings - Fork 41
Start "Communication Libraries" section #40
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
Conversation
|
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 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?
There was a problem hiding this comment.
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?
|
preview available: https://docs.tds.cscs.ch/40 |
|
preview available: https://docs.tds.cscs.ch/40 |
|
preview available: https://docs.tds.cscs.ch/40 |
|
preview available: https://docs.tds.cscs.ch/40 |
|
preview available: https://docs.tds.cscs.ch/40 |
|
preview available: https://docs.tds.cscs.ch/40 |
|
preview available: https://docs.tds.cscs.ch/40 |
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.