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

NAME

6       ibv_srq_pingpong - simple InfiniBand shared receive queue test
7
8

SYNOPSIS

10       ibv_srq_pingpong [-p port] [-d device] [-i ib port] [-s size] [-m size]
11       [-q num QPs] [-r rx depth] [-n iters] [-l sl] [-e] [-g gid index] HOST‐
12       NAME
13
14       ibv_srq_pingpong [-p port] [-d device] [-i ib port] [-s size] [-m size]
15       [-q num QPs] [-r rx depth] [-n iters] [-l sl] [-e] [-g gid index]
16
17

DESCRIPTION

19       Run a simple ping-pong test over InfiniBand via the reliable  connected
20       (RC)  transport,  using  multiple queue pairs (QPs) and a single shared
21       receive queue (SRQ).
22
23

OPTIONS

25       -p, --port=PORT
26              use TCP port PORT for initial synchronization (default 18515)
27
28       -d, --ib-dev=DEVICE
29              use IB device DEVICE (default first device found)
30
31       -i, --ib-port=PORT
32              use IB port PORT (default port 1)
33
34       -s, --size=SIZE
35              ping-pong messages of size SIZE (default 4096)
36
37       -m, --mtu=SIZE
38              path MTU SIZE (default 1024)
39
40       -q, --num-qp=NUM
41              use NUM queue pairs for test (default 16)
42
43       -r, --rx-depth=DEPTH
44              post DEPTH receives at a time (default 1000)
45
46       -n, --iters=ITERS
47              perform ITERS message exchanges (default 1000)
48
49       -l, --sl=SL
50              use SL as the service level value of the QPs (default 0)
51
52       -e, --events
53              sleep while waiting for work completion events  (default  is  to
54              poll for completions)
55
56       -g, --gid-idx=GIDINDEX
57              local port GIDINDEX
58
59       -c, --chk
60              validate received buffer
61
62

SEE ALSO

64       ibv_rc_pingpong(1),       ibv_uc_pingpong(1),       ibv_ud_pingpong(1),
65       ibv_xsrq_pingpong(1)
66
67

AUTHORS

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

BUGS

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