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

Traffic Prioritization #809

Closed
neuroscr opened this issue Sep 5, 2019 · 9 comments
Closed

Traffic Prioritization #809

neuroscr opened this issue Sep 5, 2019 · 9 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@neuroscr
Copy link
Contributor

neuroscr commented Sep 5, 2019

- Michael to build a special priority queue
- Needs the #807 refactor to be done

  • Tom will implement prioritization for different packet types to ensure a clogged router only drops user traffic instead of important network infrastructure messages
@neuroscr neuroscr added enhancement New feature or request blocked labels Sep 5, 2019
@neuroscr neuroscr added this to the 0.6 milestone Sep 5, 2019
@neuroscr neuroscr added this to To do in Enhancements via automation Sep 5, 2019
@neuroscr
Copy link
Contributor Author

Tom said it will be a per-session queues

@neuroscr
Copy link
Contributor Author

neuroscr commented Sep 10, 2019

Jason said primary reason: Don't let slow downloaders clog queues

@neuroscr
Copy link
Contributor Author

neuroscr commented Sep 11, 2019

Tom said: can happen in the logic thread. Will need to revise a bit. The receiving needs to take in account queuing, so it's not immediately tic'd, so that will need to be changed in the network thread.

@neuroscr neuroscr removed the blocked label Sep 11, 2019
@neuroscr
Copy link
Contributor Author

Tom says "Michael to build a special priority queue" is no longer necessary

@neuroscr
Copy link
Contributor Author

information from failure case in the link layer to the routing layer to properly respond to congestion

@neuroscr
Copy link
Contributor Author

best way forward is to implement CoDel
needs a new type of NACK
some discussion between HEAD vs TAIL drop
needs input on how to identify bottlenecks correctly
need to communicate between first node and last node (since it'll backup from last node to first, and we need to inform the first node asap) we can't inform destination

@neuroscr
Copy link
Contributor Author

neuroscr commented Nov 3, 2019

PR is in #873 just being reviewed

@neuroscr
Copy link
Contributor Author

Tom needs some changes in #906 which Jeff is going to break into pieces

@neuroscr
Copy link
Contributor Author

873 is merged now

Enhancements automation moved this from To do to Done Dec 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
No open projects
Enhancements
  
Done
Development

No branches or pull requests

3 participants