1IBV_XSRQ_PINGPONG(1) USER COMMANDS IBV_XSRQ_PINGPONG(1)
2
3
4
6 ibv_xsrq_pingpong - simple InfiniBand shared receive queue test
7
8
10 ibv_xsrq_pingpong [-p port] [-d device] [-i ib port] [-s size] [-m mtu]
11 [-c clients] [-n num_tests] [-l sl] [-e] [-g gid index] HOSTNAME
12
13 ibv_xsrq_pingpong [-p port] [-d device] [-i ib port] [-s size] [-m mtu]
14 [-c clients] [-n num_tests] [-l sl] [-e] [-g gid index]
15
16
18 Run a simple ping-pong test over InfiniBand via the extended reliable
19 connected (XRC) transport service, using a shared receive queue (SRQ).
20
21
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=MTU
36 use path mtu of size MTU (default 2048)
37
38 -c, --clients=CLIENTS
39 number of clients CLIENTS (on server only, default 1)
40
41 -n, --num-tests=NUM_TESTS
42 perform NUM_TESTS tests per client (default 5)
43
44 -l, --sl=SL
45 use SL as the service level value (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
56 ibv_rc_pingpong(1), ibv_uc_pingpong(1), ibv_ud_pingpong(1)
57 ibv_srq_pingpong(1)
58
59
61 Roland Dreier
62 <roland@purestorage.com>
63
64 Jarod Wilson
65 <jarod@redhat.com>
66
67
69 The network synchronization between client and server instances is
70 weak, and does not prevent incompatible options from being used on the
71 two instances. The method used for retrieving work completions is not
72 strictly correct, and race conditions may cause failures on some sys‐
73 tems.
74
75
76
77libibverbs May 24, 2016 IBV_XSRQ_PINGPONG(1)