1UDADDY(1) librdmacm UDADDY(1)
2
3
4
6 udaddy - RDMA CM datagram setup and simple ping-pong test.
7
9 udaddy [-s server_address] [-b bind_address] [-c connections]
10 [-C message_count] [-S message_size] [-p port_space]
11 udaddy -s server_address [-b bind_address] [-c connections]
12 [-C message_count] [-S message_size] [-t tos] [-p port_space]
13
15 Establishes a set of unreliable RDMA datagram communication paths
16 between two nodes using the librdmacm, optionally transfers datagrams
17 between the nodes, then tears down the communication.
18
20 -s server_address
21 The network name or IP address of the server system listening
22 for communication. The used name or address must route over an
23 RDMA device. This option must be specified by the client.
24
25 -b bind_address
26 The local network address to bind to.
27
28 -c connections
29 The number of communication paths to establish between the
30 client and server. The test uses unreliable datagram communica‐
31 tion, so no actual connections are formed. (default 1)
32
33 -C message_count
34 The number of messages to transfer over each connection.
35 (default 10)
36
37 -S message_size
38 The size of each message transferred, in bytes. This value must
39 be smaller than the MTU of the underlying RDMA transport, or an
40 error will occur. (default 100)
41
42 -t tos Indicates the type of service used for the communication. Type
43 of service is implementation dependent based on subnet configu‐
44 ration.
45
46 -p port_space
47 The port space of the datagram communication. May be either the
48 RDMA UDP (0x0111) or IPoIB (0x0002) port space. (default
49 RDMA_PS_UDP)
50
52 Basic usage is to start udaddy on a server system, then run udaddy -s
53 server_name on a client system.
54
55 Because this test maps RDMA resources to userspace, users must ensure
56 that they have available system resources and permissions. See the
57 libibverbs README file for additional details.
58
60 rdma_cm(7), ucmatose(1), mckey(1), rping(1)
61
62
63
64librdmacm 2007-05-15 UDADDY(1)