From: Sebastian Moeller <moeller0@gmx.de>
To: Brandon Applegate <brandon@burn.net>,
Alan Jenkins <alan.christopher.jenkins@gmail.com>
Cc: Bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Getting started with sqm-scripts - latency good, bandwidth decimated
Date: Wed, 20 Jan 2016 17:05:06 +0100 [thread overview]
Message-ID: <143AE017-AA48-442A-8A95-21CEE60EA27E@gmx.de> (raw)
In-Reply-To: <C261CE0A-068D-454F-8750-875317555ADE@burn.net>
[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]
Okay so at least the egress uplinks seems okay, maybe a bit too generous, at 5Mbps contracted speed, maybe 4500Kbps would be a more cautious starting point. But in essence this looks good, I fail to see the ingress ifb4eth0.666, so can offer any opinion on that.
On January 20, 2016 4:15:35 PM GMT+01:00, Brandon Applegate <brandon@burn.net> wrote:
>Here’s the output to check the rates.
>
>root@ice:/etc/sqm# head -2 eth0.666.iface.conf
>UPLINK=5000
>DOWNLINK=30000
>
>root@ice:/etc/sqm# tc class show dev eth0.666
>class htb 1:11 parent 1:1 leaf 110: prio 1 rate 128000bit ceil 1666Kbit
>burst 1600b cburst 1599b
>class htb 1:1 root rate 5000Kbit ceil 5000Kbit burst 1600b cburst 1600b
>class htb 1:10 parent 1:1 prio 0 rate 5000Kbit ceil 5000Kbit burst
>1600b cburst 1600b
>class htb 1:13 parent 1:1 leaf 130: prio 3 rate 833000bit ceil 4984Kbit
>burst 1599b cburst 1599b
>class htb 1:12 parent 1:1 leaf 120: prio 2 rate 833000bit ceil 4984Kbit
>burst 1599b cburst 1599b
>class fq_codel 110:160 parent 110:
>class fq_codel 120:1f5 parent 120:
>
>--
>Brandon Applegate - CCIE 10273
>PGP Key fingerprint:
>830B 4802 1DD4 F4F9 63FE B966 C0A7 189E 9EC0 3A74
>"SH1-0151. This is the serial number, of our orbital gun."
>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Bloat mailing list
>Bloat@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/bloat
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
[-- Attachment #2: Type: text/html, Size: 1926 bytes --]
next prev parent reply other threads:[~2016-01-20 16:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 23:33 Brandon Applegate
2016-01-20 0:09 ` Jonathan Morton
2016-01-20 0:14 ` Brandon Applegate
2016-01-20 2:36 ` Jonathan Morton
2016-01-20 17:32 ` Simon Barber
2016-01-20 10:12 ` Alan Jenkins
2016-01-20 10:15 ` Alan Jenkins
2016-01-20 11:47 ` moeller0
2016-01-20 11:43 ` moeller0
2016-01-20 12:06 ` Alan Jenkins
2016-01-20 12:25 ` moeller0
2016-01-20 14:51 ` Brandon Applegate
2016-01-20 15:10 ` moeller0
2016-01-20 15:15 ` Brandon Applegate
2016-01-20 16:05 ` Sebastian Moeller [this message]
2016-01-20 16:10 ` Brandon Applegate
2016-01-20 16:32 ` Alan Jenkins
2016-01-20 16:34 ` Brandon Applegate
2016-01-20 16:47 ` Etienne Champetier
2016-01-20 16:54 ` Brandon Applegate
2016-01-20 17:09 ` Etienne Champetier
2016-01-20 17:42 ` moeller0
2016-01-20 17:50 ` Etienne Champetier
2016-01-20 17:40 ` moeller0
2016-01-20 11:30 ` moeller0
2016-01-20 12:37 ` Rich Brown
2016-01-20 14:42 ` Brandon Applegate
2016-01-20 15:30 ` Brandon Applegate
2016-01-20 16:09 ` Sebastian Moeller
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=143AE017-AA48-442A-8A95-21CEE60EA27E@gmx.de \
--to=moeller0@gmx.de \
--cc=Bloat@lists.bufferbloat.net \
--cc=alan.christopher.jenkins@gmail.com \
--cc=brandon@burn.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