| Always nice to see you, john. 1) If we had sufficient backpressure in the ISPs provided router network driver, with "BQL" to manage the ringbuffers and fq_codel to do fq + aqm, we're mostly done, at least on the uplink. The hope has been, since most home routers run linux, that 5 years after RFC8920 entered mainline linux, it would appear in ISP gear. fq_codel is now the default on most linux distros but without the backpressure from bql or running below line rate it's not effective unless further configured or shaped. 2) I wish having your own shaper was not "a trend". bql and fq_codel are lightweight compared to shaping. 3) sch_cake solves a bunch of remaining problems: A) doing both flow and host based fairness at the same time, so your host frantically issuing http requests only gets 1/hosts the bandwidth. B) uses a deficit shaper that consistently runs at a rate slightly less than the (ubiquitous) token bucket shaper ISPs use. So it can share the same setpoint but control the queue. https://arxiv.org/abs/1804.07617 4) we have a lot of wifi devices now doing fq_codel by default. Very happy with the results.
https://arxiv.org/pdf/1703.00064.pdf Perhaps on rfc970's 40th anniversary, we can view these problems as solved! |