Diffusion FreeBSD src repository 3d0b768cc0a0

tcp: finish SACK loss recovery on sudden lack of SACK blocks
3d0b768cc0a0
Actions

Tags

None

Referenced Files

None

Subscribers

None

Description

tcp: finish SACK loss recovery on sudden lack of SACK blocks

While a receiver should continue sending SACK blocks for the
duration of a SACK loss recovery, if for some reason the
TCP options no longer contain these SACK blocks, but we
already started maintaining the Scoreboard, keep on handling
incoming ACKs (without SACK) as belonging to the SACK recovery.

Reported by: thj
Reviewed by: tuexen, transport
MFC after: 2 weeks
Sponsored by: NetApp, Inc.
Differential Revision: https://reviews.freebsd.org/D36046

(cherry picked from commit c21b7b55bea2cc2bf3b420c70a9018e703ed6f00)

Details

Provenance

Authored on Aug 31 2022, 12:49 PM

Reviewer

Differential Revision

D36046: Keep doing SACK loss recovery when ACKs suddenly lack SACK blocks

Parents

rG998c08856a4e: src.conf: Introduce WITHOUT_MACHDEP_OPTIMIZATIONS knob.

Branches

Unknown

Tags

Unknown

Reverted By

rG99c1c6755de4: Revert "tcp: finish SACK loss recovery on sudden lack of SACK blocks"

Event Timeline

rscheff committed rG3d0b768cc0a0: tcp: finish SACK loss recovery on sudden lack of SACK blocks (authored by rscheff).Sep 13 2022, 3:14 PM

rscheff added an edge: D36046: Keep doing SACK loss recovery when ACKs suddenly lack SACK blocks.Sep 14 2022, 1:09 AM

rscheff added a reverting change: rG99c1c6755de4: Revert "tcp: finish SACK loss recovery on sudden lack of SACK blocks".Sep 14 2022, 1:29 AM

Changes (1)

Path

Size

sys/

netinet/

rG3d0b768cc0a0

sys/netinet/tcp_input.c

Loading...