[Mvapich-discuss] osu_latency_mp & osu_latency_mt not working with "-d cuda" in 5.8

[Subramoni, Hari]

Hi, Carl.

Thanks for pointing this out. We appreciate it. We have updated the readme file with an acknowledgement to you.

Best,
Hari.

From: Mvapich-discuss <mvapich-discuss-bounces+subramon=cse.ohio-state.edu at lists.osu.edu> On Behalf Of Carl Ponder via Mvapich-discuss
Sent: Sunday, October 31, 2021 9:10 AM
To: mvapich-discuss at lists.osu.edu
Subject: [Mvapich-discuss] osu_latency_mp & osu_latency_mt not working with "-d cuda" in 5.8

The README from the 5.8 tarball says this
ROCm, CUDA and OpenACC Extensions to OMB
----------------------------------------
CUDA Extensions to OMB can be enable by configuring the benchmark suite with
--enable-cuda option as shown below.

    ./configure CC=/path/to/mpicc
                CXX=/path/to/mpicxx
                --enable-cuda
                --with-cuda-include=/path/to/cuda/include
                --with-cuda-libpath=/path/to/cuda/lib
    make
    make install

 .......

Similarly, OpenACC Extensions can be enabled by specifying the --enable-openacc
option.  The MPI library used should be able to support MPI communication from
buffers in GPU Device memory.

The following benchmarks have been extended to evaluate performance of
MPI communication using buffers on AMD and NVIDIA GPU devices.

    osu_bibw           - Bidirectional Bandwidth Test
    osu_bw             - Bandwidth Test
    osu_latency        - Latency Test
    osu_mbw_mr         - Multiple Bandwidth / Message Rate Test
    osu_multi_lat      - Multi-pair Latency Test
    osu_latency_mt     - Multi-threaded Latency Test
    osu_latency_mp     - Multi-process Latency Test

......

If both CUDA and OpenACC support is enabled you can switch between the modes
using the -d [cuda|openacc] option to the benchmarks. If ROCm support is
enabled, you need to use -d rocm option to make the benchmarks use this feature.
Whether a process allocates its communication buffers on the GPU device or on
the host can be controlled at run-time.  Use the -h option for more help.
The -d cuda and -d openacc options don't work with the osu_latency_mp & osu_latency_mt benchmarks.
Invalid option [-d]
Usage: osu_latency_mp [options]
.....
Also, the online documentation
https://mvapich.cse.ohio-state.edu/benchmarks/
includes the osu_latency_mt in the list but not the osu_latency_mp. It just looks like the docs need to be updated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osu.edu/pipermail/mvapich-discuss/attachments/20211101/c1d224e4/attachment-0021.html>