Lines Matching full:sacks

47  *					removing SACKs due to in sequence incoming
235 	/* skb->len may jitter because of SACKs, even if peer  in tcp_measure_rcv_mss()
281 		 * that SACKs block is variable.  in tcp_measure_rcv_mss()
1209 /* Take a notice that peer is sending D-SACKs. Skip update of data delivery
1336 /* This procedure tags the retransmission queue when SACKs arrive.
1371  * in packet stream. With SACKs we can estimate it:
1420  * ends, TCP might receive valid D-SACKs below that. As long as they reside
1440 	/* In outstanding window? ...This is valid exit for D-SACKs too.  in tcp_is_sackblock_valid()
1539 		/* Round if necessary so that SACKs cover only full MSSes  in tcp_match_skb_to_sack()
1815 			 * because later SACKs might again split them, and  in tcp_shift_skb_data()
2245 /* Emulate SACKs for SACKless connection: account for a new dupack. */
2316  * and reset tags completely, otherwise preserve SACKs. If receiver
2323 	bool is_reneg;			/* is receiver reneging on SACKs? */  in tcp_timeout_mark_lost()
2397  * remembered SACKs do not reflect real state of receiver i.e.
2427  *		we see some SACKs or dupacks. It is split of "Open"
2454  *		   and hence not ACKed. With SACKs this number is simply
2455  *		   amount of SACKed data. Even without SACKs
2500  * timestamps and D-SACKs. When we detect that some segments were
2716 /* Try to undo cwnd reduction, because D-SACKs acked all retransmitted data */
3140 	/* B. In all the states check for reneging SACKs. */  in tcp_fastretrans_alert()
4950 /* RCV.NXT advances, some SACKs should be eaten. */
4958 	/* Empty ofo queue, hence, all the SACKs are eaten. Clear. */  in tcp_sack_remove()
4972 			/* Zap this SACK, by moving forward any other SACKS. */  in tcp_sack_remove()
6893 	 * undo. If peer SACKs triggered fast recovery, we can't undo here.  in tcp_rcv_synrecv_state_fastopen()