Home
last modified time | relevance | path

Searched refs:SACK (Results 1 – 9 of 9) sorted by relevance

/Linux-v5.4/Documentation/networking/
Dsnmp_counter.rst570 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.
[all …]
Dtimestamping.txt130 cumulative acknowledgment. The mechanism ignores SACK and FACK.
305 account SACK would be more complex due to possible transmission holes
Dip-sysctl.txt498 RFC6675 recovery for SACK connections.
574 TCP tries to reduce number of SACK sent, using a timer
581 Max number of SACK that can be compressed.
582 Using 0 disables SACK compression.
2204 to send a SACK.
/Linux-v5.4/include/linux/usb/
Dr8a66597.h337 #define SACK 0x0010 /* b4: Setup acknowledge interrupt */ macro
/Linux-v5.4/drivers/usb/renesas_usbhs/
Dcommon.h186 #define SACK (1 << 4) /* Setup Transaction ACK Response Interrupt Status */ macro
Dmod.c319 if (irq_state.intsts1 & SACK) in usbhs_interrupt()
/Linux-v5.4/drivers/usb/host/
Dr8a66597-hcd.c1075 r8a66597_write(r8a66597, ~(SIGN | SACK), INTSTS1); in prepare_setup_packet()
1666 if (mask1 & SACK) { in r8a66597_irq()
1667 r8a66597_write(r8a66597, ~SACK, INTSTS1); in r8a66597_irq()
/Linux-v5.4/Documentation/networking/device_drivers/chelsio/
Dcxgb.txt120 Disabling SACK:
/Linux-v5.4/Documentation/networking/device_drivers/intel/
Dixgb.rst260 # turn SACK support off, default on