Lines Matching refs:SACK

570 The TCP protocol has two retransmission mechanisms: SACK and fast
571 recovery. They are exclusive with each other. When SACK is enabled,
572 the kernel TCP stack would use SACK, or kernel would use fast
573 recovery. The SACK is a TCP option, which is defined in `RFC2018`_,
596 A packet was acknowledged by SACK, but the receiver has dropped this
599 could drop a packet which has been acknowledged by SACK, although it is
608 if SACK is disabled. The fast recovery algorithm detects recorder by
628 The reorder packet detected by SACK. The SACK has two methods to
634 receives SACK for packet 4 and the sender doesn't retransmit the
651 A SACK points out that a retransmission packet is lost again.
693 invalid SACK and DSACK
695 When a SACK (or DSACK) block is invalid, a corresponding counter would
697 number of the SACK block. For more details, please refer the comment
699 SACK option could have up to 4 blocks, they are checked
702 `Add counters for discarded SACK blocks`_ patch has additional
705 .. _Add counters for discarded SACK blocks: https://git.kernel.org/pub/scm/linux/kernel/git/torvald…
709 This counter indicates how many SACK blocks are invalid. If the invalid
710 SACK block is caused by ACK recording, the TCP stack will only ignore
724 SACK shift
727 short). If a SACK block acrosses multiple skb, the TCP stack will try
728 to re-arrange data in these skb. E.g. if a SACK block acknowledges seq
731 SACK block acknowledges seq 10 to 20, skb1 has seq 10 to 13, skb2 has