Skip to content

quic: Improve loss detection with time threshold #5634

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

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

akhinvasara-jumptrading
Copy link
Contributor

This is very much a draft. Tests are yet unwritten. Intended to obtain feedback.

This PR improves the ability to detect losses, particulary with few packets on a connection. In addition to the packet skip threshold, it uses a time threshold to mark packets as lost.

Copy link
Contributor

@nbridge-jump nbridge-jump left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, but we never found the source of the spamming, did we?

@akhinvasara-jumptrading
Copy link
Contributor Author

lgtm, but we never found the source of the spamming, did we?

No, we didn't. Was planning to let these changes soak on mainnet to monitor before merging, to see if we still see that. All after merging the service queue heap to avoid hiding bugs here.

This reverts commit 543e6f0fb72451eb6294f249c135322e05b8a50d.
      reset next_timeout in svc_schedule

      fix retx timeout ticks/ns issue

      prep schedule in gen_frames

      CRIT if svc_timer_cnt != active_conn_cnt

      schedule idle_timeout from last_activity, not now

      test_quic_conformance: update for service heap
      fix test_quic_keep_alive
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