Lines Matching refs:ACK

146  (*) Calls use ACK packets to handle reliability.  Data packets are also
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
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
197  (*) ACK'ing is handled by the protocol driver automatically, including ping
236      the reply is transmitted with one or more sendmsgs, and then the final ACK
322 	RXRPC_ACK		-rt n/a		Final ACK received
349      This is delivered to a server application to indicate that the final ACK
645  (9) The final ACK from the client will be posted for retrieval by recvmsg()
650 	RXRPC_ACK		- indicates final ACK (no data)
779 	RXRPC_SKB_MARK_FINAL_ACK	Final ACK received for an incoming call
829      update the ACK state for the call.  The socket buffer will be freed.
886      ACK permits several packets to be ACK'd in one go.
891      generate a soft-ACK to tell the sender that it doesn't need to resend.
896      received queue have been consumed before we generate a hard-ACK to tell
898      we would send an ACK.
903      transmit it again, assuming no ACK is received from the receiver telling
915      repeating ACK and ABORT packets.