3 ms·
Very interesting, but I suspect like many of these it works best if you are only competing with only connections using the same approach. Which is probably why
by wscott 10y ago
Very interesting, but I suspect like many of these it works best if you are only competing with only connections using the same approach. Which is probably why Google is talking about using this inside their backbone.
This estimates the queues in the network and tries to keep them empty. TCP ramps until packets start dropping, so it spoils things for the BRR connection. Perhaps combined with Codel on to drop TCP packets early the two could play nicely together.
Hmm, reading the code it says it does play well with TCP, but "requires the fq ("Fair Queue") pacing packet scheduler." In fact, later it says it MUST be used with fq.
Hmm.
BTW the code is very readable and well commented.
- apenwarr 10y agoI think the need for fq is just because that's how Linux does pacing, and pacing is essential for the accuracy of measurements used by bbr.