| ... | ... | @@ -28,16 +28,7 @@ Communication APIs facilitate the communication between different computers by a |
|
|
|
|
|
|
|
LinkTest can test and benchmark different communication APIs. The communication API that LinkTest uses can be controlled via the `--mode` command-line option. Alternatively it can be specified by appending it as a suffix to the LinkTest-executable name, for example `linktest.mpi`, or it can be specified via the `LINKTEST_VCLUSTER_IMPL` environment variable.
|
|
|
|
|
|
|
|
LinkTest supports the following communication APIs:
|
|
|
|
|
|
|
|
| API | Env. Variable | Default | Description |
|
|
|
|
| ----- | -------- | ------- | ----------- |
|
|
|
|
| `mpi` | `HAVE_MPI` | Enabled | MPI |
|
|
|
|
| `ibverbs` | `HAVE_IBVERBS` | Enabled | Verbs-based implementation |
|
|
|
|
| `psm2` | `HAVE_PSM2` | Enabled | PSM2 (Omni-Path) |
|
|
|
|
| `cuda` | `HAVE_CUDA` | Enabled | NVLink (node-internal) |
|
|
|
|
| `ucp` | `HAVE_UCP` | Enabled | UCX |
|
|
|
|
| `tcp` | `HAVE_TCP` | Enabled | TCP sockets |
|
|
|
|
All supported communication APIs can be found in [Build Variables / Transport Layers](Build#build-variables-transport-layers)
|
|
|
|
|
|
|
|
Note that during LinkTest installation only desired supported communication APIs are installed by setting the corresponding environment variable to `1` to install or `0` to not install. As such a given LinkTest executable may not support all the listed communication APIs. By default all communication APIs are supported after installation, however this rarely builds successfully as most platforms do not support all communication APIs due to a lack of relevant hardware.
|
|
|
|
|
| ... | ... | |
