Skip to content

Make ingress egress ratelimit bins separate again. #20

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

Merged
merged 4 commits into from
Nov 28, 2024
Merged

Make ingress egress ratelimit bins separate again. #20

merged 4 commits into from
Nov 28, 2024

Conversation

brada4
Copy link
Contributor

@brada4 brada4 commented Nov 28, 2024

Restore rate limit bidirectionality fixing #7 which effectively halved intended packet rate (per bin)

Adds 1 byte to int32 ct id.
alternative could have been doubling rates in calculation, lets better keep in and out counts separate as before.

Signed-off-by: Andris PE neandris@gmail.com

brada4 and others added 4 commits November 19, 2024 23:16
Comment text says "downprioritize", where in fact it does reverse cs1->cs0

simple code would be
  ip dscp lt cs4 ip dsccp ne cs1
#7 applies limit to both
connection directions effectively halving intended rate

Restore rate limit bidirectionality

Adds 1 byte to 4 byte ct id in keys

Less accurate alternative could have been doubling calculated packet
rates.

Signed-off-by:
@hudra0 hudra0 merged commit e0ec8bd into hudra0:main Nov 28, 2024
@brada4
Copy link
Contributor Author

brada4 commented Nov 28, 2024

oops, ill re-base #15 on top of this if you dont manage today

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