Randall Stewart f092a3c71c So it turns out with the right window scaling you can get the code in all stacks to ... always want to do a window update, even when no data can be sent. Now in cases where you are not pacing thats probably ok, you just send an extra window update or two. However with bbr (and rack if its paced) every time the pacer goes off its going to send a "window update". Also in testing bbr I have found that if we are not responding to data right away we end up staying in startup but incorrectly holding a pacing gain of 192 (a loss). This is because the idle window code does not restict itself to only work with PROBE_BW. In all other states you dont want it doing a PROBE_BW state change. Sponsored by: Netflix Inc. Differential Revision: https://reviews.freebsd.org/D25247		2020-06-12 19:56:19 +00:00
..
bbr.c	So it turns out with the right window scaling you can get the code in all stacks to	2020-06-12 19:56:19 +00:00
rack_bbr_common.c	This fixes several skyzaller issues found with the	2020-05-15 14:00:12 +00:00
rack_bbr_common.h	This commit brings things into sync with the advancements that	2020-05-04 20:28:53 +00:00
rack.c	So it turns out with the right window scaling you can get the code in all stacks to	2020-06-12 19:56:19 +00:00
sack_filter.c	Remove all trailing white space from the BBR/Rack fold. Bits	2020-02-12 12:40:06 +00:00
sack_filter.h	This commit adds BBR (Bottleneck Bandwidth and RTT) congestion control. This	2019-09-24 18:18:11 +00:00
tcp_bbr.h	This commit brings things into sync with the advancements that	2020-05-04 20:28:53 +00:00
tcp_rack.h	This fixes a couple of skyzaller crashes. Most	2020-06-03 14:07:31 +00:00