Lines Matching refs:with

7 of AF_RXRPC family, using sendmsg() and recvmsg() with control data to send and
80  (2) provided with a protocol of the type of underlying transport they're going
130  (*) The data blobs are of indefinite size, the end of a phase is marked with a
140      replies with a "response".  If the response is successful, the security is
193      able to share connections with each other.
204      aborted with an appropriate network error passed through recvmsg().
207 Interaction with the user of the RxRPC socket:
209  (*) A socket is made into a server socket by binding an address with a
212  (*) In the client, sending a request is achieved with one or more sendmsgs,
213      followed by the reply being received with one or more recvmsgs.
216      be used in all other sendmsgs or recvmsgs associated with that call.  The
230  (*) Once the application has received the last message associated with a call,
232      client resources.  A new call can then be initiated with the same tag
235  (*) In the server, a request is received with one or more recvmsgs, then the
236      the reply is transmitted with one or more sendmsgs, and then the final ACK
237      is received with a last recvmsg.
272  (*) The server application has to provide the server socket with a keyring of
335      message or in the server by passing it in association with an RXRPC_ACCEPT
336      message.  recvmsg() passes it in conjunction with all messages except
343      received.  Either way, it must be associated with an RXRPC_USER_CALL_ID to
345      will be returned if there is no call with that user ID.
350      of a call was received from the client.  It will be associated with an
365      associated with an RXRPC_USER_CALL_ID to indicate the rejected call.
378      arrived and is awaiting acceptance.  No user ID is associated with this,
384      assign it a user ID.  It should be associated with an RXRPC_USER_CALL_ID
400      extracted from the calling process's keyrings with request_key() and
538      of sendmsg() calls, each with the following control message attached:
554      All data will be delivered with the following control message attached:
576  (2) Security is set up if desired by giving the socket a keyring with server
608      it a message for each.  This is received with recvmsg() on the server
619  (5) The server then accepts the new call by issuing a sendmsg() with two
631      be delivered with MSG_MORE flagged.
633      All data will be delivered with the following control message attached:
638      of sendmsg() calls, each with the following control messages attached:
646      when it is received.  It will take the form of a dataless message with two
656      aborted by calling sendmsg() with a dataless message with the following
715      the key bound to the socket with the RXRPC_SECURITY_KEY sockopt.  Calls
731      from AF_RXRPC's knowledge and will not be seen again in association with
770      The interceptor function itself is provided with the address of the socket
786      The remote abort message can be probed with rxrpc_kernel_get_abort_code().
787      The two error messages can be probed with rxrpc_kernel_get_error_number().
788      A new call can be accepted with rxrpc_kernel_accept_call().
790      Data messages can have their contents extracted with the usual bunch of
792      be the last one in a sequence with rxrpc_kernel_is_data_last().  When a
819      This is used to reject the first incoming call on the socket's queue with
880      The amount of time in milliseconds after receiving a packet with the