Scroll to navigation

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] [-P] [-t] [-j] [-N] 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] [-P] [-t] [-j] [-N]

DESCRIPTION

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

OPTIONS

use TCP port PORT for initial synchronization (default 18515)
use IB device DEVICE (default first device found)
use IB port PORT (default port 1)
ping-pong messages of size SIZE (default 4096)
path MTU SIZE (default 1024)
post DEPTH receives at a time (default 1000)
perform ITERS message exchanges (default 1000)
use SL as the service level value of the QP (default 0)
sleep while waiting for work completion events (default is to poll for completions)
local port GIDINDEX
use on demand paging
prefetch an ODP MR
get CQE with timestamp
validate received buffer
use device memory
use new post send WR API

SEE ALSO

ibv_uc_pingpong(1), ibv_ud_pingpong(1), ibv_srq_pingpong(1), ibv_xsrq_pingpong(1)

AUTHORS

<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.

August 30, 2005 libibverbs