On Mon, 2014-03-24 at 16:10 -0700, Dave Taht wrote: > One of my concerns is that sch_fq is (?) currently inadaquately > explored in the case of wifi - as best as I recall there were a > ton of drivers than cloned and disappeared the skb deep > in driver buffers, making fq_codel a mildly better choice...
Thats because fq_codel do not add delays (other than RR scheduling among flows). Remember, if no queue is in fq_codel itself, there nothing we can control using codel law. In the fq case, packets are held in the qdisc the needed time and delivered 'at the right time' to whatever lower device. Part of the 'original TCP bursts' are amortized by sch_fq before reaching device. TCP pacing has nothing to do with additional delays imposed in various wifi drivers. Consider a packet in wifi queue exactly as if it was already sent on the network. _______________________________________________ Bloat mailing list [email protected] https://lists.bufferbloat.net/listinfo/bloat
