FreeBSD manual

download PDF document: ibv_rc_pingpong.1.pdf

IBV_RC_PINGPONG(1) USER COMMANDS IBV_RC_PINGPONG(1)


NAME ibv_rc_pingpong - simple InfiniBand RC transport test

SYNOPSIS ibv_rc_pingpong [-p port] [-d device] [-i ib port] [-s size] [-m size] [-r rx depth] [-n iters] [-l sl] [-e] [-g gid index] [-o] [-t] HOSTNAME
ibv_rc_pingpong [-p port] [-d device] [-i ib port] [-s size] [-m size] [-r rx depth] [-n iters] [-l sl] [-e] [-g gid index] [-o] [-t]

DESCRIPTION Run a simple ping-pong test over InfiniBand via the reliable connected (RC) transport.

OPTIONS -p, --port=PORT use TCP port PORT for initial synchronization (default 18515)
-d, --ib-dev=DEVICE use IB device DEVICE (default first device found)
-i, --ib-port=PORT use IB port PORT (default port 1)
-s, --size=SIZE ping-pong messages of size SIZE (default 4096)
-m, --mtu=SIZE path MTU SIZE (default 1024)
-r, --rx-depth=DEPTH post DEPTH receives at a time (default 1000)
-n, --iters=ITERS perform ITERS message exchanges (default 1000)
-l, --sl=SL use SL as the service level value of the QP (default 0)
-e, --events sleep while waiting for work completion events (default is to poll for completions)
-g, --gid-idx=GIDINDEX local port GIDINDEX
-o, --odp use on demand paging
-t, --ts get CQE with timestamp
Roland Dreier <rolandd@cisco.com>

BUGS The network synchronization between client and server instances is weak, and does not prevent incompatible options from being used on the two instances. The method used for retrieving work completions is not strictly correct, and race conditions may cause failures on some systems.
libibverbs August 30, 2005 IBV_RC_PINGPONG(1)