1 .TH "UDADDY" 1 "2007-05-15" "librdmacm" "librdmacm" librdmacm
3 udaddy \- RDMA CM datagram setup and simple ping-pong test.
7 \fIudaddy\fR [-s server_address] [-b bind_address] [-c connections]
8 [-C message_count] [-S message_size] [-p port_space]
9 \fIudaddy\fR -s server_address [-b bind_address] [-c connections]
10 [-C message_count] [-S message_size] [-t tos] [-p port_space]
13 Establishes a set of unreliable RDMA datagram communication paths between two
14 nodes using the librdmacm, optionally transfers datagrams between the nodes,
15 then tears down the communication.
19 The network name or IP address of the server system listening for
20 communication. The used name or address must route over an RDMA device.
21 This option must be specified by the client.
24 The local network address to bind to.
27 The number of communication paths to establish between the client and server.
28 The test uses unreliable datagram communication, so no actual connections are
32 The number of messages to transfer over each connection. (default 10)
35 The size of each message transferred, in bytes. This value must be smaller
36 than the MTU of the underlying RDMA transport, or an error will occur.
40 Indicates the type of service used for the communication. Type of service
41 is implementation dependent based on subnet configuration.
44 The port space of the datagram communication. May be either the RDMA
45 UDP (0x0111) or IPoIB (0x0002) port space. (default RDMA_PS_UDP)
47 Basic usage is to start udaddy on a server system, then run
48 udaddy -s server_name on a client system.
50 Because this test maps RDMA resources to userspace, users must ensure
51 that they have available system resources and permissions. See the
52 libibverbs README file for additional details.
54 rdma_cm(7), ucmatose(1), mckey(1), rping(1)