From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/ceropackages-3.10] 27eed1: Initial changes to squash inbound diffserv and hav...
Date: Wed, 09 Apr 2014 14:29:28 -0700 [thread overview]
Message-ID: <5345bbb8839f4_499b148fd4010147a@hookshot-fe2-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/ceropackages-3.10
Commit: 27eed160a67700caae85a4c8b3fff0eaa990cd27
https://github.com/dtaht/ceropackages-3.10/commit/27eed160a67700caae85a4c8b3fff0eaa990cd27
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2014-04-09 (Wed, 09 Apr 2014)
Changed paths:
M net/sqm-scripts/files/usr/lib/sqm/functions.sh
M net/sqm-scripts/files/usr/lib/sqm/run.sh
M net/sqm-scripts/files/usr/lib/sqm/simple.qos
Log Message:
-----------
Initial changes to squash inbound diffserv and have simpler inbound
1) By default dscp values cannot be trusted e2e as multiple
providers change them in transit. So the correct "Default" for sqm
should be to reset all inbound diffserv marked values to
BE, and then reclassify.
2) It looks like the inbound rules for simple.qos were always
broken - see iptables -x -v -L for more details
3) IF you are not going to pay attention to diffserv,
it makes no sense to have a 3 tier system for inbound,
so this grabs simplest.qos's scheme and uses that if SQUASH_DSCP
is set.
4) Haven't tried updating the gui yet.
5) Bug:
It still looks like the tc based rules for diffserv *never* worked,
and I'm not sure which would be faster - iptables or diffserv
for outbound, so I wanted to fiddle with diffserv on that
and ran out of time - the code needs to use different priorities
((prio X)+1)) to work right in functions.sh
reply other threads:[~2014-04-09 21:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5345bbb8839f4_499b148fd4010147a@hookshot-fe2-cp1-prd.iad.github.net.mail \
--to=noreply@github.com \
--cc=cerowrt-commits@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