ibv_ud_pingpong(1) [debian man page]

IBV_UD_PINGPONG(1)						   USER COMMANDS						IBV_UD_PINGPONG(1)

NAME

       ibv_ud_pingpong - simple InfiniBand UD transport test

SYNOPSIS

       ibv_ud_pingpong [-p port] [-d device] [-i ib port] [-s size] [-r rx depth] [-n iters] [-l sl] [-e] HOSTNAME

       ibv_ud_pingpong [-p port] [-d device] [-i ib port] [-s size] [-r rx depth] [-n iters] [-l sl] [-e]

DESCRIPTION

       Run a simple ping-pong test over InfiniBand via the unreliable datagram (UD) 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 2048)

       -r, --rx-depth=DEPTH
	      post DEPTH receives at a time (default 500)

       -n, --iters=ITERS
	      perform ITERS message exchanges (default 1000)

       -l, --sl=SL
	      send messages with service level SL (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_srq_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_UD_PINGPONG(1)

CURLOPT_FTPPORT(3)					     curl_easy_setopt options						CURLOPT_FTPPORT(3)

NAME

       CURLOPT_FTPPORT - make FTP transfer active

SYNOPSIS

       #include <curl/curl.h>

       CURLcode curl_easy_setopt(CURL *handle, CURLOPT_FTPPORT, char *spec);

DESCRIPTION

       Pass a pointer to a zero terminated string as parameter. It specifies that the FTP transfer will be made actively and the given string will
       be used to get the IP address to use for the FTP PORT instruction.

       The PORT instruction tells the remote server to connect to our specified IP address. The string may be a plain IP address, a host  name,  a
       network	interface  name  (under Unix) or just a '-' symbol to let the library use your system's default IP address. Default FTP operations
       are passive, and thus won't use PORT.

       The address can be followed by a ':' to specify a port, optionally followed by a '-' to specify a port range.  If the port specified is	0,
       the  operating  system  will  pick  a  free port.  If a range is provided and all ports in the range are not available, libcurl will report
       CURLE_FTP_PORT_FAILED for the handle.  Invalid port/range settings are ignored.	IPv6 addresses followed by a port or portrange have to	be
       in brackets.  IPv6 addresses without port/range specifier can be in brackets.

       Examples with specified ports:

	 eth0:0
	 192.168.1.2:32000-33000
	 curl.se:32123
	 [::1]:1234-4567

       You disable PORT again and go back to using the passive version by setting this option to NULL.

       The application does not have to keep the string around after setting this option.

DEFAULT

       NULL

PROTOCOLS

       FTP

EXAMPLE

       TODO

AVAILABILITY

       Port range support was added in 7.19.5

RETURN VALUE

       Returns CURLE_OK if the option is supported, CURLE_UNKNOWN_OPTION if not, or CURLE_OUT_OF_MEMORY if there was insufficient heap space.

SEE ALSO

       CURLOPT_FTP_USE_EPRT(3), CURLOPT_FTP_USE_EPSV(3),

libcurl 7.54.0							 December 21, 2016						CURLOPT_FTPPORT(3)