1IBV_UD_PINGPONG(1) USER COMMANDS IBV_UD_PINGPONG(1)
2
3
4
6 ibv_ud_pingpong - simple InfiniBand UD transport test
7
8
10 ibv_ud_pingpong [-p port] [-d device] [-i ib port] [-s size] [-r rx
11 depth] [-n iters] [-l sl] [-e] [-g gid index] HOSTNAME
12
13 ibv_ud_pingpong [-p port] [-d device] [-i ib port] [-s size] [-r rx
14 depth] [-n iters] [-l sl] [-e] [-g gid index]
15
16
18 Run a simple ping-pong test over InfiniBand via the unreliable datagram
19 (UD) transport.
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 2048)
34
35 -r, --rx-depth=DEPTH
36 post DEPTH receives at a time (default 500)
37
38 -n, --iters=ITERS
39 perform ITERS message exchanges (default 1000)
40
41 -l, --sl=SL
42 send messages with service level SL (default 0)
43
44 -e, --events
45 sleep while waiting for work completion events (default is to
46 poll for completions)
47
48 -g, --gid-idx=GIDINDEX
49 local port GIDINDEX
50
51 -c, --chk
52 validate received buffer
53
54
56 ibv_rc_pingpong(1), ibv_uc_pingpong(1), ibv_srq_pingpong(1),
57 ibv_xsrq_pingpong(1)
58
59
61 Roland Dreier
62 <rolandd@cisco.com>
63
64
66 The network synchronization between client and server instances is
67 weak, and does not prevent incompatible options from being used on the
68 two instances. The method used for retrieving work completions is not
69 strictly correct, and race conditions may cause failures on some sys‐
70 tems.
71
72
73
74libibverbs August 30, 2005 IBV_UD_PINGPONG(1)