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]  [-P]  [-t]
12       HOSTNAME
13
14       ibv_rc_pingpong  [-p port] [-d device] [-i ib port] [-s size] [-m size]
15       [-r rx depth] [-n iters] [-l sl] [-e] [-g gid index] [-o] [-P] [-t]
16
17

DESCRIPTION

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

OPTIONS

24       -p, --port=PORT
25              use TCP port PORT for initial synchronization (default 18515)
26
27       -d, --ib-dev=DEVICE
28              use IB device DEVICE (default first device found)
29
30       -i, --ib-port=PORT
31              use IB port PORT (default port 1)
32
33       -s, --size=SIZE
34              ping-pong messages of size SIZE (default 4096)
35
36       -m, --mtu=SIZE
37              path MTU SIZE (default 1024)
38
39       -r, --rx-depth=DEPTH
40              post DEPTH receives at a time (default 1000)
41
42       -n, --iters=ITERS
43              perform ITERS message exchanges (default 1000)
44
45       -l, --sl=SL
46              use SL as the service level value of the QP (default 0)
47
48       -e, --events
49              sleep  while  waiting  for work completion events (default is to
50              poll for completions)
51
52       -g, --gid-idx=GIDINDEX
53              local port GIDINDEX
54
55       -o, --odp
56              use on demand paging
57
58       -P, --prefetch=
59              prefetch an ODP MR
60
61       -t, --ts
62              get CQE with timestamp
63
64       -c, --chk
65              validate received buffer
66
67

SEE ALSO

69       ibv_uc_pingpong(1),      ibv_ud_pingpong(1),       ibv_srq_pingpong(1),
70       ibv_xsrq_pingpong(1)
71
72

AUTHORS

74       Roland Dreier
75              <rolandd@cisco.com>
76
77

BUGS

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