From: Dave Taht <dave.taht@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] tc -s qdisc questions
Date: Thu, 14 May 2015 16:41:56 -0700 [thread overview]
Message-ID: <CAA93jw4JnT5veiSPGFu9dSUrsJmseV+cCC-j6dodAEg4P6OPSA@mail.gmail.com> (raw)
In-Reply-To: <55552014.2010808@darbyshire-bryant.me.uk>
On Thu, May 14, 2015 at 3:22 PM, Kevin Darbyshire-Bryant
<kevin@darbyshire-bryant.me.uk> wrote:
> Hi Chaps,
>
> Further to Dave's recent request for 'tc -s qdisc' stats looking at drops vs
> ecn marks, please could someone take a look at these and explain to this
> idiot quite what is going on? This is a particularly slow & ratty ADSL line
> providing my parents internet 'service'. Before I got hold of it with
> OpenWrt CC trunk + cake jammed in it, 6 seconds of bufferbloat was not
> uncommon. I'm using the default sqm scripts that arrive with the
> 'ceropackages' repo (used as a source of patched iproute2, cake, etc) In
> essence 2 questions: 1) Why no ECN marks, only drops?
http://www.bufferbloat.net/projects/cerowrt/wiki/Enable_ECN
> 2) What falls into
> diffserv class 0 (alias, why has nothing used it?)
depends.
>
> Your time, patience etc is greatly appreciated.
>
> Kevin
>
> root@Router:~# tc -s qdisc show dev pppoa-wan
> qdisc cake 803a: root refcnt 2 bandwidth 256Kbit diffserv4 flows
> Sent 1928303 bytes 12121 pkt (dropped 73, overlimits 6915 requeues 0)
> backlog 0b 0p requeues 0
> Class 0 Class 1 Class 2 Class 3
> rate 256Kbit 240Kbit 192Kbit 64Kbit
> target 70.5ms 75.2ms 94.0ms 282.0ms
> interval 564.0ms 601.6ms 752.0ms 2.3s
> Pk delay 0us 91.4ms 17.5ms 3.2ms
> Av delay 0us 2.9ms 2.9ms 53us
> Sp delay 0us 5us 136us 7us
> pkts 0 11754 408 32
> way inds 0 0 0 0
> way miss 0 347 404 5
> way cols 0 0 0 0
> bytes 0 1973100 28163 6537
> drops 0 73 0 0
> marks 0 0 0 0
> qdisc ingress ffff: parent ffff:fff1 ----------------
> Sent 8221609 bytes 11969 pkt (dropped 6, overlimits 0 requeues 0)
> backlog 0b 0p requeues 0
> root@Router:~# tc -s qdisc show dev ifb4pppoa-wan
> qdisc cake 803b: root refcnt 2 bandwidth 1512Kbit besteffort flows
> Sent 7597496 bytes 11494 pkt (dropped 482, overlimits 10487 requeues 0)
> backlog 0b 0p requeues 0
> Class 0
> rate 1512Kbit
> target 12.0ms
> interval 112.0ms
> Pk delay 3.3ms
> Av delay 289us
> Sp delay 5us
> pkts 11976
> way inds 0
> way miss 769
> way cols 0
> bytes 8270163
> drops 482
> marks 0
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
--
Dave Täht
Open Networking needs **Open Source Hardware**
https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67
next prev parent reply other threads:[~2015-05-14 23:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 22:22 Kevin Darbyshire-Bryant
2015-05-14 23:37 ` Jonathan Morton
2015-05-14 23:41 ` Dave Taht [this message]
2015-05-15 8:16 ` Kevin Darbyshire-Bryant
2015-05-15 8:55 ` Mikael Abrahamsson
2015-05-15 16:45 ` Dave Taht
2015-05-17 20:23 ` Kevin Darbyshire-Bryant
2015-05-18 5:46 ` Mikael Abrahamsson
2015-05-18 8:09 ` Kevin Darbyshire-Bryant
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=CAA93jw4JnT5veiSPGFu9dSUrsJmseV+cCC-j6dodAEg4P6OPSA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=kevin@darbyshire-bryant.me.uk \
/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