1IBV_SRQ_PINGPONG(1) USER COMMANDS IBV_SRQ_PINGPONG(1)
2
3
4
6 ibv_srq_pingpong - simple InfiniBand shared receive queue test
7
8
10 ibv_srq_pingpong [-p port] [-d device] [-i ib port] [-s size] [-q num
11 QPs] [-r rx depth] [-n iters] [-l sl] [-e] HOSTNAME
12
13 ibv_srq_pingpong [-p port] [-d device] [-i ib port] [-s size] [-q num
14 QPs] [-r rx depth] [-n iters] [-l sl] [-e]
15
16
18 Run a simple ping-pong test over InfiniBand via the reliable connected
19 (RC) transport, using multiple queue pairs (QPs) and a single shared
20 receive queue (SRQ).
21
22
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 -q, --num-qp=NUM
37 use NUM queue pairs for test (default 16)
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 QPs (default 0)
47
48 -e, --events
49 sleep while waiting for work completion events (default is to
50 poll for completions)
51
52
54 ibv_rc_pingpong(1), ibv_uc_pingpong(1), ibv_ud_pingpong(1)
55
56
58 Roland Dreier
59 <rolandd@cisco.com>
60
61
63 The network synchronization between client and server instances is
64 weak, and does not prevent incompatible options from being used on the
65 two instances. The method used for retrieving work completions is not
66 strictly correct, and race conditions may cause failures on some sys‐
67 tems.
68
69
70
71libibverbs August 30, 2005 IBV_SRQ_PINGPONG(1)