Searched refs:SACK (Results 1 – 7 of 7) sorted by relevance
568 The TCP protocol has two retransmission mechanisms: SACK and fast569 recovery. They are exclusive with each other. When SACK is enabled,570 the kernel TCP stack would use SACK, or kernel would use fast571 recovery. The SACK is a TCP option, which is defined in `RFC2018`_,594 A packet was acknowledged by SACK, but the receiver has dropped this597 could drop a packet which has been acknowledged by SACK, although it is606 if SACK is disabled. The fast recovery algorithm detects recorder by626 The reorder packet detected by SACK. The SACK has two methods to632 receives SACK for packet 4 and the sender doesn't retransmit the649 A SACK points out that a retransmission packet is lost again.[all …]
650 RFC6675 recovery for SACK connections.742 TCP tries to reduce number of SACK sent, using a timer750 timer used by SACK compression. This gives extra time757 Max number of SACK that can be compressed.758 Using 0 disables SACK compression.3097 to send a SACK.
140 cumulative acknowledgment. The mechanism ignores SACK and FACK.375 account SACK would be more complex due to possible transmission holes
187 #define SACK (1 << 4) /* Setup Transaction ACK Response Interrupt Status */ macro
297 if (irq_state.intsts1 & SACK) in usbhs_interrupt()
323 #define SACK 0x0010 /* b4: Setup acknowledge interrupt */ macro
129 Disabling SACK::