The state of fq_codel and cake in 2022(blog.cerowrt.org) |
The state of fq_codel and cake in 2022(blog.cerowrt.org) |
Having cake on the upstream means I can push containers, send horribly large backups with multiple TCP streams, etc - all without choking meeting calls - it really makes the internet so much better to use when you do more than one thing at once.
Linux on the same platform will only forward 642.71 Kpps.
Using 3 of the four cores for VPP yields 15.1Mpps forwarded IPv4 while consuming 19W.
tnsr with a GUI as a “new pfSense” is being worked on now.
No idea (yet) what I’m going to do about codel / PIE / cake though.
In the non-shaping case, say going two 10Gbit ports into one...
what I had expected (in the future I saw in 2015) was that the FQ/AQM would be offloaded to hardware, and that vpp/ddpk would also get a timestamp and 5 tuple hash from the receive path's HW.
This would be a plus for a userspace router implementation, as presently in linux we timestamp on entry to the exit queue, not on all the overheads of routing lookup, and other processing from the read from the rx ring.