Lines Matching refs:SACK

568 The TCP protocol has two retransmission mechanisms: SACK and fast
569 recovery. They are exclusive with each other. When SACK is enabled,
570 the kernel TCP stack would use SACK, or kernel would use fast
571 recovery. The SACK is a TCP option, which is defined in `RFC2018`_,
594 A packet was acknowledged by SACK, but the receiver has dropped this
597 could drop a packet which has been acknowledged by SACK, although it is
606 if SACK is disabled. The fast recovery algorithm detects recorder by
626 The reorder packet detected by SACK. The SACK has two methods to
632 receives SACK for packet 4 and the sender doesn't retransmit the
649 A SACK points out that a retransmission packet is lost again.
691 invalid SACK and DSACK
693 When a SACK (or DSACK) block is invalid, a corresponding counter would
695 number of the SACK block. For more details, please refer the comment
697 SACK option could have up to 4 blocks, they are checked
700 18f02545a9a1 ("[TCP] MIB: Add counters for discarded SACK blocks")
705 This counter indicates how many SACK blocks are invalid. If the invalid
706 SACK block is caused by ACK recording, the TCP stack will only ignore
720 SACK shift
723 short). If a SACK block acrosses multiple skb, the TCP stack will try
724 to re-arrange data in these skb. E.g. if a SACK block acknowledges seq
727 SACK block acknowledges seq 10 to 20, skb1 has seq 10 to 13, skb2 has