Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

dtest(1) [centos man page]

dtest(1)							   USER COMMANDS							  dtest(1)

NAME
dtest - simple uDAPL send/receive and RDMA test SYNOPSIS
dtest [-P provider] [-b buf size] [-B burst count][-v] [-c] [-p] [-d] [-s] dtest [-P provider] [-b buf size] [-B burst count][-v] [-c] [-p] [-d] [-h HOSTNAME] DESCRIPTION
dtest is a simple test used to exercise and verify the uDAPL interfaces. At least two instantiations of the test must be run. One acts as the server and the other the client. The server side of the test, once invoked listens for connection requests, until timing out or killed. Upon receipt of a cd connection request, the connection is established, the server and client sides exchange information necessary to per- form RDMA writes and reads. OPTIONS
-P=PROVIDER use PROVIDER to specify uDAPL interface using /etc/dat.conf (default OpenIB-cma) -b=BUFFER_SIZE use buffer size BUFFER_SIZE for RDMA(default 64) -B=BURST_COUNT use busrt count BURST_COUNT for interations (default 10) -v, verbose output(default off) -c, use consumer notification events (default off) -p, use polling (default wait for event) -d, delay in seconds before close (default off) -s, run as server (default - run as server) -h=HOSTNAME use HOSTNAME to specify server hostname or IP address (default - none) EXAMPLES
dtest -P OpenIB-cma -v -s Starts a server process with debug verbosity using provider OpenIB-cma. dtest -P OpenIB-cma -h server1-ib0 Starts a client process, using OpenIB-cma provider to connect to hostname server1-ib0. SEE ALSO
dapltest(1) AUTHORS
Arlin Davis <ardavis@ichips.intel.com> BUGS
uDAPL 1.2 February 23, 2007 dtest(1)

Check Out this Related Man Page

RSTREAM(1)							     librdmacm								RSTREAM(1)

NAME
rstream - streaming over RDMA ping-pong test. SYNOPSIS
rstream [-s server_address] [-b bind_address] [-B buffer_size] [-I iterations] [-C transfer_count] [-S transfer_size] [-p server_port] [-T test_option] DESCRIPTION
Uses the streaming over RDMA protocol (rsocket) to connect and exchange data between a client and server application. OPTIONS
-s server_address The network name or IP address of the server system listening for connections. 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. -B buffer_size Indicates the size of the send and receive network buffers. -I iterations The number of times that the specified number of messages will be exchanged between the client and server. (default 1000) -C transfer_count The number of messages to transfer from the client to the server and back again on each iteration. (default 1) -S transfer_size The size of each send transfer, in bytes. (default 1000) If 'all' is specified, rstream will run a series of tests of various sizes. -p server_port The server's port number. -T test_option Specifies test parameters. Available options are: s | socket - uses standard socket calls to transfer data a | async - uses asynchronous operation (e.g. select / poll) b | blocking - uses blocking calls f | fork - fork server processing (forces -T s option) n | nonblocking - uses non-blocking calls v | verify - verifies data transfers NOTES
Basic usage is to start rstream on a server system, then run rstream -s server_name on a client system. By default, rstream will run a series of latency and bandwidth performance tests. Specifying a different iterations, transfer_count, or transfer_size will run a user customized test using default values where none have been specified. 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) librdmacm 2011-11-16 RSTREAM(1)
Man Page