@MikroTik staff. Yes, this is good news, this is a massive step forward in the industry (Yes, I am serious). But there’s a problem.
MikroTik RouterOS Linux queuing doesn’t support BQL:
- https://lwn.net/Articles/469652/
- https://www.bufferbloat.net/projects/bloat/wiki/BQL_enabled_drivers/
- http://forum.mikrotik.com/t/qos-hardware-offloading-qos-hw/166573/1
Artificial bufferbloat shows up in bufferbloat tests when we use fq_codel on MikroTik RouterOS on physical wired interfaces, the same problem doesn’t happen on Debian for example with BQL.
Solution for MikroTik:
Please add BQL support.
Once you add BQL support, we get performance boost (CPU usage will drop) + long-term viability of fq_codel for service provider networks and also enterprise.
Next step is industry adoption of fq_codel on ASICs, I don’t know if this is possible or not with Marvell ASICs though.
Regarding ECN, in my testing in production networks, leaving ECN marking enabled by default works better in the long run, assuming BQL is well-supported by the underlying platform. Overall, I would suggest leaving ECN enabled.