From: moeller0 <moeller0@gmx.de>
To: Alan Jenkins <alan.christopher.jenkins@gmail.com>
Cc: Brandon Applegate <brandon@burn.net>, Bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Getting started with sqm-scripts - latency good, bandwidth decimated
Date: Wed, 20 Jan 2016 13:25:14 +0100 [thread overview]
Message-ID: <E4FB7954-6905-4A9D-B473-7F240188ABA1@gmx.de> (raw)
In-Reply-To: <569F785F.5010801@gmail.com>
Hi Alan,
> On Jan 20, 2016, at 13:06 , Alan Jenkins <alan.christopher.jenkins@gmail.com> wrote:
> [...]
> No offense to your work on sqm-scripts.
None taken ;) I really just want to use the opportunity to a) get Brandon up and running and b) fix any short-comings on sqm-scripts on the way.
>
>
> 1) It's just in case the problem is *outside* of sqm-scripts, it could be useful to try the minimum commands necessary to demonstrate the problem.
I fully agree.
> Maybe it's unfair but I assumed running on a PC is also a less tested case, as well as the "firewall on a stick" part.
You are spot on, both are rather exotic test cases at least as far as reports go; that is what intrigues me even more ;)
>
> Equally, since AFAICT Brandon hasn't had a working AQM setup on this box before. It could be useful if the Gentoo script works, to prove that AQM + fq_codel can work correctly on Brandon's box.
I guess since we just thought sqm-scripts to allow verbose debugging output (into a log file) I thought it is time to advertise that feature ;)
>
> If the Gentoo script _wasn't_ working, that's when I'd suggest tearing it down e.g. to eliminate fq_codel as an issue. Rather than specify fifo explicitly, just don't run the fq_codel command (assuming that actually does something sensible, which can be checked using `tc qdisc`).
>
>
> 2) More specifically, you didn't mention trying "simplest.qos". This would i) simplify the setup we're trying to debug, and ii) it might show if there's a bug with the more complex bandwidth calculations / assignments in "simple.qos”.
Oh, you had mentioned that already and I fully agree that getting a simple test cases going is going to help a lot. So we violently agree ;)
>
>
> And again - I suggest starting by checking `tc class show dev eth0.666`, because it's not a 100% obvious command, and we don't want to miss if there are bad rates there :).
Again, I fully agree, I guess I should have mentioned that I have no genuinely new advice but rather just recommendations for slight variations on the way. Sorry for muddying the water here.
Best Regards
Sebastian
>
>
> Alan
next prev parent reply other threads:[~2016-01-20 12:25 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 [this message]
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
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=E4FB7954-6905-4A9D-B473-7F240188ABA1@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