-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ecn and babeld test #13
Comments
so even filtering out these many routes on the couch server goes boom... let's try compiling the xnor branch! root@gw1:~# ip route |
4096 routes on mips. ebpf and atomic updates are needed everywhere 32392 1 root R 2924 5% 31% /usr/sbin/babeld -I -c /etc/babeld.co |
So I configured flent to send 100 non-ecn'd flows, while sqm was fq_codeling at 40Mbit, with 4096 routes from rtod. Basically all babel packets get marked on every burst.
qdisc fq_codel 110: parent 1:10 limit 1001p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
maxpacket 4542 drop_overlimit 0 new_flow_count 4872 ecn_mark 48 memory_used 316448
root@dancer:~/git/rtod# tc -s qdisc show dev eno1 | grep ecn
qdisc fq_codel 110: parent 1:10 limit 1001p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
maxpacket 4542 drop_overlimit 0 new_flow_count 7906 ecn_mark 98 memory_used 302976
tcp_nup-2018-10-03T221206.114668.flent.gz
Normally what would happen to babel on a test like this is it would lose connectivity at some point. Let's try that!
The text was updated successfully, but these errors were encountered: