1IBV_UC_PINGPONG(1)               USER COMMANDS              IBV_UC_PINGPONG(1)
2
3
4

NAME

6       ibv_uc_pingpong - simple InfiniBand UC transport test
7
8

SYNOPSIS

10       ibv_uc_pingpong  [-p  port]  [-d  device] [-i ib port] [-s size] [-r rx
11       depth] [-n iters] [-e] HOSTNAME
12
13       ibv_uc_pingpong [-p port] [-d device] [-i ib port]  [-s  size]  [-r  rx
14       depth] [-n iters] [-e]
15
16

DESCRIPTION

18       Run  a simple ping-pong test over InfiniBand via the reliable connected
19       (RC) transport.
20
21

OPTIONS

23       -p, --port=PORT
24              use TCP port PORT for initial synchronization (default 18515)
25
26       -d, --ib-dev=DEVICE
27              use IB device DEVICE (default first device found)
28
29       -i, --ib-port=PORT
30              use IB port PORT (default port 1)
31
32       -s, --size=SIZE
33              ping-pong messages of size SIZE (default 4096)
34
35       -r, --rx-depth=DEPTH
36              post DEPTH receives at a time (default 1000)
37
38       -n, --iters=ITERS
39              perform ITERS message exchanges (default 1000)
40
41       -e, --events
42              sleep while waiting for work completion events  (default  is  to
43              poll for completions)
44
45

SEE ALSO

47       ibv_rc_pingpong(1), ibv_ud_pingpong(1), ibv_srq_pingpong(1)
48
49

AUTHORS

51       Roland Dreier
52              <rolandd@cisco.com>
53
54

BUGS

56       The  network  synchronization  between  client  and server instances is
57       weak, and does not prevent incompatible options from being used on  the
58       two  instances.  The method used for retrieving work completions is not
59       strictly correct, and race conditions may cause failures on  some  sys‐
60       tems.
61
62
63
64libibverbs                      August 30, 2005             IBV_UC_PINGPONG(1)