1RDS-INFO(1)               BSD General Commands Manual              RDS-INFO(1)
2

NAME

4     rds-info — display information from the RDS kernel module
5

SYNOPSIS

7     rds-info [-v] [-cknrstIT]
8
9

DESCRIPTION

11     The rds-info utility presents various sources of information that the RDS
12     kernel module maintains.  When run without any optional arguments
13     rds-info will output all the information it knows of.  When options are
14     specified then only the information associated with those options is dis‐
15     played.
16
17     The options are as follows:
18
19     -v      Requests verbose output. When this option is given, some classes
20             of information will display additional data.
21
22
23     -c      Display global counters.  Each counter increments as its event
24             occurs.  The counters may not be reset.  The set of supported
25             counters may change over time.
26
27
28             CounterName
29               The name of the counter.  These names come from the kernel and
30               can change depending on the capability of the kernel module.
31
32             Value
33               The number of times that the counter has been incremented since
34               the kernel module was loaded.
35
36
37     -k      Display all the RDS sockets in the system.  There will always be
38             one socket listed that is neither bound to nor connected to any
39             addresses because rds-info itself uses an unbound socket to col‐
40             lect information.
41
42
43             BoundAddr, BPort
44               The IP address and port that the socket is bound to.  0.0.0.0 0
45               indicates that the socket has not been bound.
46
47             ConnAddr, CPort
48               The IP address and port that the socket is connected to.
49               0.0.0.0 0 indicates that the socket has not been connected.
50
51             SndBuf, RcvBuf
52               The number of bytes of message payload which can be queued for
53               sending or receiving on the socket, respectively.
54
55             Inode
56               The number of the inode object associated with the socket. Can
57               be used to locate the process owning a given socket by search‐
58               ing /proc/*/fd for open files referencing a socket with this
59               inode number.
60
61
62     -n      Display all RDS connections.  RDS connections are maintained
63             between nodes by transports.
64
65
66             LocalAddr
67               The IP address of this node.  For connections that originate
68               and terminate on the same node the local address indicates
69               which address initiated the connection establishment.
70
71             RemoteAddr
72               The IP address of the remote end of the connection.
73
74             NextTX
75               The sequence number that will be given to the next message that
76               is sent over the connection.
77
78             NextRX
79               The sequence number that is expected from the next message to
80               arrive over the connection.  Any incoming messages with
81               sequence numbers less than this will be dropped.
82
83             Flg
84               Flags which indicate the state of the connection.
85
86               s
87                 A process is currently sending a message down the connection.
88
89               c
90                 The transport is attempting to connect to the remote address.
91
92               C
93                 The connection to the remote host is connected and active.
94
95
96     -r, -s, -t
97             Display the messages in the receive, send, or retransmit queues
98             respectively.
99
100             LocalAddr, LPort
101               The local IP address and port on this node associated with the
102               message. For sent messages this is the source address, for
103               receive messages it is the destination address.
104
105             RemoteAddr, RPort
106               The remote IP address and port associated with the message. For
107               sent messages this is the destination address, for receive mes‐
108               sages it is the source address.
109
110             Seq
111               The sequence number of the message.
112
113             Bytes
114               The number of bytes in the message payload.
115
116             The following information sources are dependent on specific
117             transports which may not always be available.
118
119
120     -I      Display the IB connections which the IB transport is using to
121             provide RDS connections.
122
123
124             LocalAddr
125               The local IP address of this connection.
126
127             RemoteAddr
128               The remote IP address of this connection.
129
130             LocalDev
131               The local IB Global Identifier, printed in IPv6 address syntax.
132
133             RemoteDev
134               The remote IB Global Identifier, printed in IPv6 address syn‐
135               tax.
136
137             If verbose output is requested, per-connection settings such as
138             the maximum number of send and receive work requests will be dis‐
139             played in addition.
140
141
142     -T      Display the TCP sockets which the TCP transport is using to pro‐
143             vide RDS connections.
144
145
146             LocalAddr, LPort
147               The local IP address and port of this socket.
148
149             RemoteAddr, RPort
150               The remote IP address and port that this socket is connected
151               to.
152
153             HdrRemain
154               The number of bytes that must be read off the socket to com‐
155               plete the next full RDS header.
156
157             DataRemain
158               The number of bytes that must be read off the socket to com‐
159               plete the data payload of the message which is being received.
160
161             SentNxt
162               The TCP sequence number of the first byte of the last message
163               that we sent down the connection.
164
165             ExpectedUna
166               The TCP sequence number of the byte past the last byte of the
167               last message that we sent down the connection.  When we see
168               that the remote side has acked up to this byte then we know
169               that the remote side has received all our RDS messages.
170
171             SeenUna
172               The TCP sequence number of the byte past the last byte which
173               has been acked by the remote host.
174
175
176BSD                            October 30, 2006                            BSD
Impressum