Skip to content

Fixed bug that led to inaccurate max_packet_length based on TCP Options#853

Merged
zakird merged 1 commit intomainfrom
phillip/tcp-syn-inaccurate-max-packet-len
Apr 18, 2024
Merged

Fixed bug that led to inaccurate max_packet_length based on TCP Options#853
zakird merged 1 commit intomainfrom
phillip/tcp-syn-inaccurate-max-packet-len

Conversation

@phillip-stephens
Copy link
Contributor

The module's max_packet_length is used for accurately computing the send rate to stay under any user-given bandwidth limitations.

This bug meant that the packet length was only accurate for the case where no TCP options were used (--probe-args="none") and incorrect for all other options.

Testing

Before fix, --probe-args="windows" -B 1G and --probe-args="linux" -B 1G would give the same send rate on a non-bandwidth constrained system, even though windows sends 8 bytes less per probe packet.

After fix, the same test results in 1.34 Mpps for windows and 1.24 Mpps for linux.

@phillip-stephens phillip-stephens marked this pull request as ready for review April 18, 2024 19:05
@phillip-stephens phillip-stephens requested a review from zakird April 18, 2024 19:05
@zakird zakird merged commit 7c8ddfd into main Apr 18, 2024
@zakird zakird deleted the phillip/tcp-syn-inaccurate-max-packet-len branch April 18, 2024 19:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants