ibv_srq_pingpong(1) [centos 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)

HTC(1)							      General Commands Manual							    HTC(1)

NAME

       htc - httptunnel client

SYNOPSIS

       htc [options] host[:port]

DESCRIPTION

       This manual page briefly documents the htc command.

       htc  sets  up a httptunnel connection to PORT at HOST (default port is 8888).  When a connection is made, I/O is redirected from the source
       specified by the --device or --forward-port switch to the tunnel.

OPTIONS

       The program follows the usual GNU command line syntax, with long options starting with two dashes (`-').  A summary of options are included
       below.

       -h, --help
	      Show summary of options.

       -c, --content-length BYTES
	      use HTTP PUT requests of BYTES size (k, M, and G postfixes recognized)

       -d, --device DEVICE
	      use DEVICE for input and output

       -F, --forward-port PORT
	      use TCP port PORT for input and output

       -k, --keep-alive SECONDS
	      send keepalive bytes every SECONDS seconds (default is 5)

       -M, --max-connection-age SEC
	      maximum time a connection will stay open is SEC seconds (default is 300)

       -S, --strict-content-length
	      always write Content-Length bytes in requests

       -A, --proxy-authorization USER:PASSWORD
	      proxy authorization

       -z, --proxy-authorization-file FILE
	      proxy authorization file

       -B, --proxy-buffer-size BYTES
	      assume a proxy buffer size of BYTES bytes (k, M, and G postfixes recognized)

       -P, --proxy HOSTNAME[:PORT]
	      use a HTTP proxy (default port is 8080)

       -T, --timeout TIME
	      timeout, in milliseconds, before sending padding to a buffering proxy

       -U, --user-agent STRING
	      specify User-Agent value in HTTP requests

       -V, --version
	      output version information and exit

       -w, --no-daemon
	      don't fork into the background

AUTHOR

       This manual page was contributed by Teemu Hukkanen <tjhukkan@iki.fi>, and was originally written for the Debian GNU/Linux system.

																	    HTC(1)