... | @@ -43,18 +43,17 @@ FZJ Linktest (<<<VERSION>>>) |
... | @@ -43,18 +43,17 @@ FZJ Linktest (<<<VERSION>>>) |
|
```
|
|
```
|
|
where `<<<VERSION>>>` is the three part version of Linktest executable. Like the `-h` or `--help` option Linktest does not need to be executed with this option. This option supersedes all other aside from the `-h` or `--help` option.
|
|
where `<<<VERSION>>>` is the three part version of Linktest executable. Like the `-h` or `--help` option Linktest does not need to be executed with this option. This option supersedes all other aside from the `-h` or `--help` option.
|
|
|
|
|
|
`-w/--num-warmup-messages`: Specifies that the following integer indicates the number of warm-up messages to use to warm up a connection before testing it. When not printing help or version information this command-line argument is required.
|
|
`-w`or `--num-warmup-messages`: Specifies that the following integer indicates the number of warm-up messages to use to warm up a connection before testing it. When not printing help or version information this command-line argument is required.
|
|
|
|
|
|
`-n/--num-messages`: Specifies that the following integer indicates the number of messages measurements should be averaged over during testing. When not printing help or version information this command-line argument is required.
|
|
`-n` or `--num-messages`: Specifies that the following integer indicates the number of messages measurements should be averaged over during testing. When not printing help or version information this command-line argument is required.
|
|
|
|
|
|
`-s/--size-messages`: Specifies that the following integer indicates the message size in bytes for testing. When not printing help or version information this command-line argument is required.
|
|
`-s` or `--size-messages`: Specifies that the following integer indicates the message size in bytes for testing. When not printing help or version information this command-line argument is required.
|
|
|
|
|
|
`-m` or `--mode`: Specifies that the following ASCII string indicates the communication API to use for testing. Alternatively the communication API can be extracted from the extension of the Linktest executable name or from the `LINKTEST_VCLUSTER_IMPL` environment variable. When multiple ways of specifying the communication API are used then `-m` or `--mode` supersedes the linktest executable extension, which in turn also supersedes the `LINKTEST_VCLUSTER_IMPL` environment variable.
|
|
`-m` or `--mode`: Specifies that the following ASCII string indicates the communication API to use for testing. Alternatively the communication API can be extracted from the extension of the Linktest executable name or from the `LINKTEST_VCLUSTER_IMPL` environment variable. When multiple ways of specifying the communication API are used then `-m` or `--mode` supersedes the linktest executable extension, which in turn also supersedes the `LINKTEST_VCLUSTER_IMPL` environment variable.
|
|
|
|
|
|
`--all-to-all`: Specifies that the following integer, if non-zero, indicates that all-to-all testing should be done before and after the main Linktest test if the used communication API is MPI.
|
|
`--all-to-all`: Specifies that the following integer, if non-zero, indicates that all-to-all testing should be done before and after the main Linktest test if the used communication API is MPI.
|
|
|
|
|
|
`--bidirectional`: Specifies that the following integer, if non-zero, indicates that testing should occur
|
|
`--bidirectional`: Specifies that the following integer, if non-zero, indicates that testing should occur bidirectionally instead of semi-directionally, which is the default.
|
|
bidirectionally instead of semi-directionally, which is the default.
|
|
|
|
|
|
|
|
`--bisection`: Specifies that the following integer, if non-zero, indicates that the tasks for testing should be split in two halves and that testing should only occur between these two. This is useful for determining bisection bandwidths.
|
|
`--bisection`: Specifies that the following integer, if non-zero, indicates that the tasks for testing should be split in two halves and that testing should only occur between these two. This is useful for determining bisection bandwidths.
|
|
|
|
|
... | @@ -104,7 +103,7 @@ Except for the MPI and the node-internal CUDA transport layer, all layers utiliz |
... | @@ -104,7 +103,7 @@ Except for the MPI and the node-internal CUDA transport layer, all layers utiliz |
|
|
|
|
|
With any transport layer but MPI or intra-node CUDA it is important to make sure that the PMI (not MPI) environment is correctly set up. The easiest way to achieve this using slurm is: `srun --mpi=pmi2` or `srun --mpi=pmix`. If this option is not available or not supported by slurm please consult the relevant PMI documentation for your system.
|
|
With any transport layer but MPI or intra-node CUDA it is important to make sure that the PMI (not MPI) environment is correctly set up. The easiest way to achieve this using slurm is: `srun --mpi=pmi2` or `srun --mpi=pmix`. If this option is not available or not supported by slurm please consult the relevant PMI documentation for your system.
|
|
|
|
|
|
## WIP: Supported Combinations of Communication APIS & Various Options
|
|
## WIP: Supported Combinations of Communication APIs & Various Options
|
|
|
|
|
|
!!! WORK IN PROGRESS !!!
|
|
!!! WORK IN PROGRESS !!!
|
|
|
|
|
... | | ... | |