News for hackers. Stuff that matters.
Re:BBR, the new kid on the TCP block by kev009 on Tuesday May 09, 2017 @03:28PM (#14303111)
Your terminology seems a bit strange to me, the way I've seen these discussed:

CoDel is an AQM (Active Queue Management) algorithm - it decides what packets to drop and when to drop them as a packet queue fills. This is most relevant at the hop with a bottle neck link.

BBR and reno etc are TCP congestion control algorithms or less frequently called congestion avoidance algorithms - they manipulate the window size and attempt to avoid congestion using different takes on congestion signaling (i.e.loss based reno, delay based for vegas, model based for bbr). This is most relevant from the sender side.

Scheduling would be more advanced queuing disciplines (for QoS or flow based fair queuing) and packet pacers. Queuing disciplines can apply to any bottle neck link, pacing is most useful sender side.

Re:BBR, the new kid on the TCP block by throwasehasdwi on Wednesday May 10, 2017 @02:05PM (#14310231)
CoDel is packet scheduling. It just dynamically creates "classes" for each flow to determine which ones are overfilling the buckets and selectively drops from those streams.

I try to talk about these things in a way that's easy for lay people to understand. Even among programmers QoS and packet scheduling are a niche topic

Re:BBR, the new kid on the TCP block by _av8l on Wednesday May 10, 2017 @04:28PM (#14311351)
Re:BBR, the new kid on the TCP block by throwasehasdwi on Monday May 15, 2017 @12:29PM (#14342863)
right you are! My apologies, my familiarly with CoDel is limited to the Linux implementation