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

NAME

6       ibv_rc_pingpong - simple InfiniBand RC transport test
7
8

SYNOPSIS

10       ibv_rc_pingpong  [-p port] [-d device] [-i ib port] [-s size] [-m size]
11       [-r rx depth] [-n iters] [-l sl] [-e] [-g gid index] [-o] [-t] HOSTNAME
12
13       ibv_rc_pingpong [-p port] [-d device] [-i ib port] [-s size] [-m  size]
14       [-r rx depth] [-n iters] [-l sl] [-e] [-g gid index] [-o] [-t]
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       -m, --mtu=SIZE
36              path MTU SIZE (default 1024)
37
38       -r, --rx-depth=DEPTH
39              post DEPTH receives at a time (default 1000)
40
41       -n, --iters=ITERS
42              perform ITERS message exchanges (default 1000)
43
44       -l, --sl=SL
45              use SL as the service level value of the QP (default 0)
46
47       -e, --events
48              sleep while waiting for work completion events  (default  is  to
49              poll for completions)
50
51       -g, --gid-idx=GIDINDEX
52              local port GIDINDEX
53
54       -o, --odp
55              use on demand paging
56
57       -t, --ts
58              get CQE with timestamp
59
60       -c, --chk
61              validate received buffer
62
63

SEE ALSO

65       ibv_uc_pingpong(1),       ibv_ud_pingpong(1),      ibv_srq_pingpong(1),
66       ibv_xsrq_pingpong(1)
67
68

AUTHORS

70       Roland Dreier
71              <rolandd@cisco.com>
72
73

BUGS

75       The network synchronization between  client  and  server  instances  is
76       weak,  and does not prevent incompatible options from being used on the
77       two instances.  The method used for retrieving work completions is  not
78       strictly  correct,  and race conditions may cause failures on some sys‐
79       tems.
80
81
82
83libibverbs                      August 30, 2005             IBV_RC_PINGPONG(1)
Impressum