Repository navigation
Bound WG/AWG TCP windows for high-RTT paths - #1
Merged
Merged
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.
Native WG/AWG TCP rings limit high-RTT throughput even when CPU has headroom. Use 2 MiB RX/TX rings within a process-wide additional-capacity budget: 32 MiB on ARM64/x86 (8 large connections), 8 MiB on 32-bit MIPS (2). Connections beyond the allowance retain the old 128/64 KiB rings; closing/failing connections returns the reservation. No configuration or AWG crypto/obfuscation changes.
Also make the existing FakeIP exit-gate test independent of external DNS: its old google.com query hit an earlier evaluate action. The explicit FakeIP-domain query passes with loopback only.
Validation:
Known limits: one earlier 70 ms download fell to 11.64 Mbit/s and remains unlocalized; ten captured retries were normal. Larger windows trade memory and saturation latency for speed. The allowance is not a total RSS cap. Physical low-RAM MIPS and long-running production memory behavior were not benchmarked.
See docs/wireguard-tcp-windows-2026-11-11.md for evidence and limits. GitHub CI passed all five jobs on 9f6c722: Linux including privileged gates, differential, ARM64, x86_64 and MIPS cross-builds. This draft prepares the change for a separate release decision.