Lines Matching +full:re +full:- +full:attached
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
81 (2) provided with a protocol of the type of underlying transport they're going
82 to use - currently only PF_INET is supported.
106 (#) Client-originating packets are marked, thus a transport endpoint can be
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
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.
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
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,
554 socket used - usually IPv4 but it can also be IPv6 [TODO].
560 .srx_service = 0, /* we're a client */
569 non-privileged port will be used. A UDP port may be shared between
571 per-RxRPC virtual connection.
599 of sendmsg() calls, each with the following control message attached:
620 All data will be delivered with the following control message attached:
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.
701 attached::
707 the time it is accepted - in which case the first call still on the queue
726 All data will be delivered with the following control message attached:
734 of sendmsg() calls, each with the following control messages attached:
745 control messages attached:
757 control messages attached:
775 The AF_RXRPC module also provides an interface for use by in-kernel utilities
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).
1087 aborted and -ETIME or -ETIMEDOUT will be returned.
1108 request-ack flag set before we honour the flag and actually send the
1118 generate a soft-ACK to tell the sender that it doesn't need to resend.
1123 received queue have been consumed before we generate a hard-ACK to tell
1160 unconsumed received packets we're willing to hold in memory for any
1165 The maximum packet MTU size that we're willing to receive in bytes. This
1166 indicates to the peer whether we're willing to accept jumbo packets.
1170 The maximum number of packets that we're willing to accept in a jumbo
1171 packet. Non-terminal packets in a jumbo packet must contain a four byte