Lines Matching +full:slew +full:- +full:time +full:- +full:us
1 .. SPDX-License-Identifier: GPL-2.0
7 The RxRPC protocol driver provides a reliable two-phase transport on top of UDP
38 RxRPC is a two-layer protocol. There is a session layer which provides
44 +-------------+
46 +-------------+
48 +-------------+
50 +-------------+
52 +-------------+
60 (2) A two-phase protocol. The client transmits a blob (the request) and then
82 to use - currently only PF_INET is supported.
106 (#) Client-originating packets are marked, thus a transport endpoint can be
124 connection at any one time.
126 (#) Calls are two-phase and asymmetric: the client sends its request data,
137 (#) Security is negotiated on a per-connection basis. The connection is
149 (#) There are two types of positive acknowledgment: hard-ACKs and soft-ACKs.
150 A hard-ACK indicates to the far side that all the data received to a point
151 has been received and processed; a soft-ACK indicates that the data has
152 been received but may yet be discarded and re-requested. The sender may
153 not discard any transmittable packets until they've been hard-ACK'd.
155 (#) Reception of a reply data packet implicitly hard-ACK's all the data
159 received and the final hard-ACK on the last packet of the reply has
162 (#) An call may be aborted by either end at any time up to its completion.
181 (#) Each connection is retained for a certain amount of time [tunable] after
186 time [tunable] after the last connection using it discarded, in case a new
189 (#) A client-side connection is only shared between calls if they have
191 would otherwise share the connection). Non-secured calls would also be
194 (#) A server-side connection is shared if the client says it is.
209 non-zero service ID.
285 making progress at accepting packets within a reasonable time such that we
287 client to accept at least one packet per 2*RTT time period.
301 (b) it meets a non-data message,
331 RXRPC_USER_CALL_ID sr- User ID App's call specifier
333 RXRPC_ACK -rt n/a Final ACK received
334 RXRPC_NET_ERROR -rt error num Network error on call
335 RXRPC_BUSY -rt n/a Call rejected (server busy)
336 RXRPC_LOCAL_ERROR -rt error num Local error encountered
337 RXRPC_NEW_CALL -r- n/a New call received
338 RXRPC_ACCEPT s-- n/a Accept new call
339 RXRPC_EXCLUSIVE_CALL s-- n/a Make an exclusive client call
340 RXRPC_UPGRADE_SERVICE s-- n/a Client call can be upgraded
341 RXRPC_TX_LENGTH s-- data len Total length of Tx data
372 errno-class integer value will be included in the control message data
386 errno-class integer value will be included in the control message data
407 This is used to indicate that a client call should be made on a one-off
436 message type supported. At run time this can be queried by means of the
478 encrypted - which includes the actual packet length.
494 This is a read-only option that writes an int into the buffer indicating
503 (security index 2 - rxkad). This requires the rxkad module to be loaded and,
517 uint32_t expiry; /* time at which expires */
554 socket used - usually IPv4 but it can also be IPv6 [TODO].
569 non-privileged port will be used. A UDP port may be shared between
571 per-RxRPC virtual connection.
622 RXRPC_USER_CALL_ID - specifies the user ID for this call
633 the service - otherwise it will be altered to indicate the service ID the
650 socket used - usually IPv4.
707 the time it is accepted - in which case the first call still on the queue
775 The AF_RXRPC module also provides an interface for use by in-kernel utilities
779 rather than having to open a whole slew of sockets, one for each key it
818 non-NULL).
829 with this call (or -1 if unknown at this point). Setting the data size
831 saving a copy. The value may not be less than -1.
842 allocated; if it is set, the function may return -ERESTARTSYS.
882 exclusively to in-kernel virtual addresses. msg.msg_flags may be given
915 emptied and want_more was false; and -EAGAIN if the function needs to be
958 The skb->mark field indicates the type of message:
1005 a BUSY message. -ENODATA is returned if there were no incoming calls.
1006 Other errors may be returned if the call had been aborted (-ECONNABORTED)
1007 or had timed out (-ETIME).
1038 Get the RTT time to the peer in use by a call. The value returned is in
1087 aborted and -ETIME or -ETIMEDOUT will be returned.
1107 The amount of time in milliseconds after receiving a packet with the
1108 request-ack flag set before we honour the flag and actually send the
1117 The amount of time in milliseconds after receiving a new packet before we
1118 generate a soft-ACK to tell the sender that it doesn't need to resend.
1122 The amount of time in milliseconds after all the packets currently in the
1123 received queue have been consumed before we generate a hard-ACK to tell
1129 The amount of time in milliseconds after transmitting a packet before we
1131 us they got it.
1135 The maximum amount of time in seconds that a call may be in progress
1140 The amount of time in seconds before we remove a dead call from the call
1146 The amount of time in seconds after a connection was last used before we
1153 The amount of time in seconds after a transport was last used before we
1171 packet. Non-terminal packets in a jumbo packet must contain a four byte