Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ibv_srq_pingpong(1) [debian man page]

IBV_SRQ_PINGPONG(1)						   USER COMMANDS					       IBV_SRQ_PINGPONG(1)

NAME
ibv_srq_pingpong - simple InfiniBand shared receive queue test SYNOPSIS
ibv_srq_pingpong [-p port] [-d device] [-i ib port] [-s size] [-q num QPs] [-r rx depth] [-n iters] [-l sl] [-e] HOSTNAME ibv_srq_pingpong [-p port] [-d device] [-i ib port] [-s size] [-q num QPs] [-r rx depth] [-n iters] [-l sl] [-e] DESCRIPTION
Run a simple ping-pong test over InfiniBand via the reliable connected (RC) transport, using multiple queue pairs (QPs) and a single shared receive queue (SRQ). 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) -q, --num-qp=NUM use NUM queue pairs for test (default 16) -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 QPs (default 0) -e, --events sleep while waiting for work completion events (default is to poll for completions) SEE ALSO
ibv_rc_pingpong(1), ibv_uc_pingpong(1), ibv_ud_pingpong(1) AUTHORS
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_SRQ_PINGPONG(1)

Check Out this Related Man Page

UDADDY(1)							     librdmacm								 UDADDY(1)

NAME
udaddy - RDMA CM datagram setup and simple ping-pong test. SYNOPSIS
udaddy [-s server_address] [-b bind_address] [-c connections] [-C message_count] [-S message_size] [-p port_space] udaddy -s server_address [-b bind_address] [-c connections] [-C message_count] [-S message_size] [-t tos] [-p port_space] DESCRIPTION
Establishes a set of unreliable RDMA datagram communication paths between two nodes using the librdmacm, optionally transfers datagrams between the nodes, then tears down the communication. OPTIONS
-s server_address The network name or IP address of the server system listening for communication. The used name or address must route over an RDMA device. This option must be specified by the client. -b bind_address The local network address to bind to. -c connections The number of communication paths to establish between the client and server. The test uses unreliable datagram communication, so no actual connections are formed. (default 1) -C message_count The number of messages to transfer over each connection. (default 10) -S message_size The size of each message transferred, in bytes. This value must be smaller than the MTU of the underlying RDMA transport, or an error will occur. (default 100) -t tos Indicates the type of service used for the communication. Type of service is implementation dependent based on subnet configura- tion. -p port_space The port space of the datagram communication. May be either the RDMA UDP (0x0111) or IPoIB (0x0002) port space. (default RDMA_PS_UDP) NOTES
Basic usage is to start udaddy on a server system, then run udaddy -s server_name on a client system. Because this test maps RDMA resources to userspace, users must ensure that they have available system resources and permissions. See the libibverbs README file for additional details. SEE ALSO
rdma_cm(7), ucmatose(1), mckey(1), rping(1) librdmacm 2007-05-15 UDADDY(1)
Man Page