Lines Matching refs:received

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
159      received and the final hard-ACK on the last packet of the reply has
203  (*) If an ICMP error is received, all calls affected by that error will be
213      followed by the reply being received with one or more recvmsgs.
230  (*) Once the application has received the last message associated with a call,
235  (*) In the server, a request is received with one or more recvmsgs, then the
237      is received with a last recvmsg.
266  (*) When the kernel has received and set up an incoming call, it sends a
288      (a) it meets the end of that call's received data,
321 	RXRPC_ABORT		srt Abort code	Abort code to issue/received
322 	RXRPC_ACK		-rt n/a		Final ACK received
326 	RXRPC_NEW_CALL		-r- n/a		New call received
343      received.  Either way, it must be associated with an RXRPC_USER_CALL_ID to
350      of a call was received from the client.  It will be associated with an
608      it a message for each.  This is received with recvmsg() on the server
646      when it is received.  It will take the form of a dataless message with two
755  (*) Intercept received RxRPC messages.
779 	RXRPC_SKB_MARK_FINAL_ACK	Final ACK received for an incoming call
843      to be received for a call (true will be returned if it does, false
896      received queue have been consumed before we generate a hard-ACK to tell
903      transmit it again, assuming no ACK is received from the receiver telling
933      unconsumed received packets we're willing to hold in memory for any