I don't think I pushed out the 6in4 patch into the build. Hell, I forgot to tag it too. Remind me to take a vacation next vacation?
If these patches aren't in your build, it looks like we are indeed only using one class for fq_codel 6in4 traffic and thus are reverting to nearly pure codel behavior rather than fq_codel. I might be getting good at reading the patterns here - it looks like this is fq_codel rather than nfq_codel? # target/linux/generic/patches-3.8/677-flow_dissector-Add-6in4-support-to-hash-keys.patch # target/linux/generic/patches-3.8/678-Handle-encapsulated-ipv6-better.patch # target/linux/generic/patches-3.8/678-remove-bad-timeout-logic-in-fast-recovery.patch as tc -s class show dev ge00 output during the test seems to show only one or two tc classes in use. But a better test if you are using simplest.qos, rather than simplest.qos, would be the 4BE test. On Sun, Jun 16, 2013 at 11:56 AM, Toke Høiland-Jørgensen <[email protected]> wrote: > Dave Taht <[email protected]> writes: > >> I am curious: Is there a current user of cero using simplest.qos, >> tunneling ipv6 via hurricane or 6to4, that can hammer it with multiple >> ipv6 streams (as in the rrul test)? (If you have rrul and ipv6, you >> can force it to do pure ipv6 testing with the -6 option.) > > Attaching a plot of rrul over ipv6 while running cerowrt-3.8.13-17 (or > my own build based on it that, is), and some output of tc -s class show > dev ge00 while the test was running. > > IPv4 pings stay flat at 45ms to the same host while the test is running. > > -Toke > -- Dave Täht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html _______________________________________________ Cerowrt-devel mailing list [email protected] https://lists.bufferbloat.net/listinfo/cerowrt-devel
