From: Dave Taht <dave.taht@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] CS1 behavior in diffserv4
Date: Fri, 19 Jun 2015 19:19:25 -0700 [thread overview]
Message-ID: <CAA93jw7PaMvsGYAWrHvZBDp8gKdzF=X_MKtdM7SA4nteMR47zw@mail.gmail.com> (raw)
I went and fixed transmission (though not cleanly) to emit CS1. It
took a while to find the right entry point, and sure enough, it was
not calling the right thing on udp.
Dumb quick patch:
http://snapon.lab.bufferbloat.net/~cero3/fixtransmission.patch
So, great, I could test what I wanted.
I have to admit I thought diffserv4 put CS1 in class 3? (haven't
looked) (seems more likely we are not matching tos properly in the
first place. Because diffserv8 is mostly class 0 also.)
root@ranger:~# tc -s qdisc show dev eth2
qdisc cake 8011: root refcnt 9 bandwidth 10Mbit diffserv4 flows raw
Sent 316759388 bytes 245396 pkt (dropped 10653, overlimits 456732 requeues 0)
backlog 39088b 27p requeues 0
Class 0 Class 1 Class 2 Class 3
rate 10Mbit 9375Kbit 7500Kbit 2500Kbit
target 5.0ms 5.0ms 5.0ms 7.3ms
interval 100.0ms 100.0ms 100.0ms 102.3ms
Pk delay 86.8ms 20.3ms 192us 291us
Av delay 18.8ms 6.5ms 3us 4us
Sp delay 4.4ms 1.1ms 3us 4us
pkts 219623 36390 2 61
way inds 25724 427 0 0
way miss 2719 2126 2 27
way cols 0 0 0 0
bytes 289564164 41102703 180 7131
drops 10577 76 0 0
marks 0 0 0 0
qdisc ingress ffff: parent ffff:fff1 ----------------
Sent 23422815 bytes 204407 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
--
Dave Täht
worldwide bufferbloat report:
http://www.dslreports.com/speedtest/results/bufferbloat
And:
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast
next reply other threads:[~2015-06-20 2:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-20 2:19 Dave Taht [this message]
2015-06-20 2:40 ` Jonathan Morton
2015-06-20 2:50 ` Dave Taht
2015-06-20 2:57 ` Dave Taht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw7PaMvsGYAWrHvZBDp8gKdzF=X_MKtdM7SA4nteMR47zw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox