General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Kristian Kielhofner <kris@kriskinc.com>
Cc: Jonathan Morton <chromatix99@gmail.com>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Cake "out of tree" on Debian
Date: Sun, 29 Jan 2017 10:06:43 -0800	[thread overview]
Message-ID: <CAA93jw6RJ0OOYvCZd3XMnC2is9QV_uGOcGT_3Yejv=-50atmKA@mail.gmail.com> (raw)
In-Reply-To: <CAKDfjgfNjm2RqdtUn-_eyHPkOVMWMK5D+x3XBRPLu0Z47KZ_Rw@mail.gmail.com>

On Sun, Jan 29, 2017 at 9:48 AM, Kristian Kielhofner <kris@kriskinc.com> wrote:
> On Sun, Jan 29, 2017 at 12:42 PM, Dave Taht <dave.taht@gmail.com> wrote:
>> tc should not be showing ?diffserv?
>>
>> did you pull your tc from here? https://github.com/dtaht/tc-adv -
>> fixed this yesterday, or so I thought.
>>
>> Also: I just refreshed iproute to head and rebased - (I needed working
>> ra expires support, and it's long past time we updated - regrettably
>> lede is on 4.4, can't change that, there). It's generally safe to be
>> running a later iproute2 than the kernel you have.
>>
>> https://github.com/dtaht/iproute2-head-cake
>>
>
> Now:
>
> UP:
> qdisc cake 8003: root refcnt 9 bandwidth 22Mbit diffserv3
> triple-isolate rtt 100.0ms raw
>  Sent 12868692 bytes 8521 pkt (dropped 0, overlimits 10941 requeues 0)
>  backlog 7570b 5p requeues 0
>  memory used: 44320b of 4Mb
>  capacity estimate: 22Mbit
>                  Bulk   Best Effort      Voice
>   thresh      1375Kbit      22Mbit    5500Kbit
>   target        13.2ms       5.0ms       5.0ms
>   interval     108.2ms     100.0ms      10.0ms
>   pk_delay         0us       7.0ms         0us
>   av_delay         0us       2.7ms         0us
>   sp_delay         0us       465us         0us
>   pkts               0        8530           1
>   bytes              0    12883790          42
>   way_inds           0           0           0
>   way_miss           0          10           1
>   way_cols           0           0           0
>   drops              0           0           0
>   marks              0           0           0
>   sp_flows           0           0           0
>   bk_flows           0           1           0
>   un_flows           0           0           0
>   max_len            0       10598          42
>
> qdisc ingress ffff: parent ffff:fff1 ----------------
>  Sent 264453 bytes 4795 pkt (dropped 0, overlimits 0 requeues 0)
>  backlog 0b 0p requeues 0


Groovy. I thought you were "Mr. VOIP"?

While the default fq scheme works really well in cake, if you test
marking packets as voip (EF, CS4,CS6,CS7,VA), it will end up in the
diffserv3 voice queue.

asterisk used to have an encapsulating protocol called iax2, which
generated a single flow as backhaul - is that still deployed?

We have a tool in flent based on dit-itg to test this. It's a bit
painful to setup the first time. I've longed to have a full
asterisk/freeswitch/jitsy test setup to look harder at voip/video
characteristics.

There are also now several as yet underdocumented options in cake:

"nat" will look at flows before they are natted so as to isolate them better.
When combined with the dual-dsthost or dual-srchost option (depending
on traffic direction) that gives you per host fq, along with per-flow
fq.

(nat triple-isolate should also do this but we're still sorting out a
bug on that:
https://github.com/dtaht/sch_cake/issues/46
)

wash: washes out dscp markings. Helpful when your provider (:cough:
comcast) remarks nearly all traffic to CS1.

I just found that appear.in is using the new "goog" marker, which
marks all videoconferencing traffic as AF41, which is more or less
appropriately handled in the "diffserv4" model.

In general I have always had good results with the simplest
(besteffort or diffserv3) settings.

There's also new support for a docsis mode using the new "mpu" idea.

https://github.com/dtaht/sch_cake/pull/45

>
> DOWN:
> qdisc cake 8004: root refcnt 2 bandwidth 130Mbit besteffort
> triple-isolate rtt 100.0ms raw
>  Sent 331715 bytes 4797 pkt (dropped 0, overlimits 610 requeues 0)
>  backlog 0b 0p requeues 0
>  memory used: 1792b of 6500000b
>  capacity estimate: 130Mbit
>                  Tin 0
>   thresh       130Mbit
>   target         5.0ms
>   interval     100.0ms
>   pk_delay        13us
>   av_delay         1us
>   sp_delay         0us
>   pkts            4797
>   bytes         331715
>   way_inds           0
>   way_miss           9
>   way_cols           0
>   drops              0
>   marks              0
>   sp_flows           0
>   bk_flows           1
>   un_flows           0
>   max_len          198

Blow it up. Tell us what happens. :)

>
> --
> Kristian Kielhofner



-- 
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org

  reply	other threads:[~2017-01-29 18:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-29  2:48 Kristian Kielhofner
2017-01-29  4:51 ` Y
2017-01-29  5:00 ` Y
2017-01-29 10:50 ` Jonathan Morton
2017-01-29 17:36   ` Kristian Kielhofner
2017-01-29 17:42     ` Dave Taht
2017-01-29 17:48       ` Kristian Kielhofner
2017-01-29 18:06         ` Dave Taht [this message]
2017-01-30 17:00           ` Kristian Kielhofner

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='CAA93jw6RJ0OOYvCZd3XMnC2is9QV_uGOcGT_3Yejv=-50atmKA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=kris@kriskinc.com \
    /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