Documentation/networking/rds.rst

11 and will hopefully help you find your way around the code.
49 	socket. The next section will cover the details. At any rate,
58 	does not change. RDS will tolerate IPs moving around (eg in
87 	This is a soft limit rather than a hard limit - RDS will
89 	takes the queue length over the limit. However, it will also
100 	Sends a message to the indicated recipient. The kernel will
104 	An attempt to send a message that exceeds SO_SNDSIZE will
108 	of queued bytes over the SO_SNDSIZE threshold will return
112 	as "congested" will return ENOBUFS.
136 	to any destination, RDS will always signal POLLOUT as long as
140 	However, the kernel will refuse to accept messages to
141 	a destination marked congested - in this case you will loop
153 	and the remote host is unreachable, RDS will keep trying forever.
163 	value, RDS_TRANS_NONE will be returned on an unbound socket.
168 	implicitly (via bind(2)) will return an error of EOPNOTSUPP.
169 	An attempt to set SO_RDS_TRANSPORT to RDS_TRANS_NONE will
329   connection will be dropped and re-established.
331   Dropping a connection while packets are queued will cause queued or
408   connection. RDS sockets will be attached to a path based on some hash
410   socket will be sent over the attached path using TCP to segment/reassemble
438   number of paths supported by the sender. The "probe" ping packet will
440   The receiver of a ping from RDS_FLAG_PROBE_PORT will thus immediately
445   If the rcvr is not mprds-capable, the exthdr in the ping will be
446   ignored.  In this case the pong will not have any exthdrs, so the sender