Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set upper bound on {active, N} settings #48

Merged
merged 1 commit into from
Oct 24, 2024
Merged

Set upper bound on {active, N} settings #48

merged 1 commit into from
Oct 24, 2024

Conversation

ferd
Copy link
Owner

@ferd ferd commented Oct 24, 2024

On a particularly quick network with wide buffers, it appears we can overflow the number and crash arbitrary connections.

A few thousands packets ought to be enough to still reach decent speeds without killing the underlying stack.

On a particularly quick network with wide buffers, it appears we can
overflow the number and crash arbitrary connections.

A few thousands packets ought to be enough to still reach decent speeds
without killing the underlying stack.
@ferd ferd merged commit 3775cd6 into main Oct 24, 2024
1 check passed
@ferd ferd deleted the set-max-active-recv branch October 24, 2024 16:57
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.

1 participant