Tenderlink: Backpressure full ACK tracking window - #35
Open
endophysics wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ACK-window panic is caused by the transport layer continuing to send packets after its ACK-tracking ring is full:
That condition can fail under congestion, loss, or delayed ACK processing. It means the sender has too many unacknowledged packets outstanding for the fixed-size tracking window.
ACK_TRACKING_PACKET_CAPACITYfor the fixed ACK ring size.saturating_sub()when measuring outstanding ACK-tracked packets.This preserves the existing ACK-ring design but makes congestion behavior non-fatal: instead of panicking when the sender outruns ACK tracking, Tenderlink pauses outbound sends until capacity is available again.