From: Dennis Fedtke <dennisfedtke@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] overhead and mpu
Date: Thu, 7 Sep 2017 09:58:20 +0200 [thread overview]
Message-ID: <84ff1b59-ec93-5862-c5e4-d03b50483961@gmail.com> (raw)
In-Reply-To: <E59912B1-174F-4E62-8AFF-BF1D644EF184@gmx.de>
Hi Sebastian,
here is the outout:
config queue
option debug_logging '0'
option interface 'eth1.100'
option qdisc 'cake'
option enabled '1'
option qdisc_advanced '1'
option qdisc_really_really_advanced '1'
option linklayer 'none'
option egress_ecn 'NOECN'
option upload '19000'
option verbosity '5'
option ingress_ecn 'ECN'
option script 'layer_cake.qos'
option download '150000'
option squash_ingress '1'
option squash_dscp '1'
option iqdisc_opts 'docsis nat'
option eqdisc_opts 'docsis nat'
But also see my last email please.
it seems that both devices use different default overhead (14 vs 18)
Thanks.
Am 07.09.2017 um 09:47 schrieb Sebastian Moeller:
> Hi Dennis,
>
>> On Sep 7, 2017, at 06:11, Dennis Fedtke <dennisfedtke@gmail.com> wrote:
>>
>> Hi everyone!
>>
>> thanks for your answers again.
>>
>> So what about from should i expect from using the docsis keyword?
>> (This layer cake script + nat docsis set in advanced config)
>>
>> tc -s qdisc show dev eth1.100:
>> qdisc cake 8064: root refcnt 2 bandwidth 19Mbit diffserv3 triple-isolate nat rtt 100.0ms raw mpu 64
>> Sent 246233450 bytes 1316430 pkt (dropped 65, overlimits 126706 requeues 0)
>> backlog 0b 0p requeues 0
>> memory used: 2372672b of 4Mb
>> capacity estimate: 19Mbit
>> Bulk Best Effort Voice
>> thresh 1187Kbit 19Mbit 4750Kbit
>> target 15.3ms 5.0ms 5.0ms
>> interval 110.3ms 100.0ms 10.0ms
>> pk_delay 0us 298us 10us
>> av_delay 0us 13us 2us
>> sp_delay 0us 1us 1us
>> pkts 0 1315692 803
>> bytes 0 246260830 59314
>> way_inds 0 733 0
>> way_miss 0 5012 29
>> way_cols 0 0 0
>> drops 0 65 0
>> marks 0 0 0
>> sp_flows 0 1 0
>> bk_flows 0 0 0
>> un_flows 0 0 0
>> max_len 0 1514 405
>>
>> tc -s qdisc show dev ifb4eth1.100
>> qdisc cake 8065: root refcnt 2 bandwidth 150Mbit diffserv3 triple-isolate nat wash rtt 100.0ms noatm overhead 18 via-ethernet mpu 64
>> Sent 869520280 bytes 2153104 pkt (dropped 30, overlimits 270811 requeues 0)
>> backlog 0b 0p requeues 0
>> memory used: 624320b of 7500000b
>> capacity estimate: 150Mbit
>> Bulk Best Effort Voice
>> thresh 9375Kbit 150Mbit 37500Kbit
>> target 5.0ms 5.0ms 5.0ms
>> interval 100.0ms 100.0ms 10.0ms
>> pk_delay 121us 448us 1us
>> av_delay 40us 158us 0us
>> sp_delay 2us 2us 0us
>> pkts 58805 1362429 731900
>> bytes 77433974 748216627 43914060
>> way_inds 0 118167 0
>> way_miss 5 5911 3
>> way_cols 0 0 0
>> drops 1 29 0
>> marks 0 0 0
>> sp_flows 0 0 0
>> bk_flows 0 0 1
>> un_flows 0 0 0
>> max_len 1486 1514 90
>>
>> Why is there no overhead showing for egress?
> Could you post post the output of "cat /etc/config/sqm" (assuming you use LEDE/OpenWrt); i have a hunch that you might have forgotten to put the docsis keyword into both advanced configuration fields (or there is a typo n one of those words).
>
>
>> Why is there overhead18 + via-ethernet showing for ingress?
> This tells you that cake is using ethernet_payload + 18 bytes overhead, and that it automatically effectively subtracted the 14 bytes overhead the kernel added before applying its 18 bytes (so that you do not need to worry about how much the kernel added).
>
> BTW, cake reports the maximum of the pkt_len field of all packets as max_len and on ethernet interfaces the kernel automatically adds 14 bytes (already to skb->len), this is why you see max_len 1514 instead of 1500. If you use tc's stab method for overhead accounting things will look different, as stab will add the full header size to pkt_len, so using tc stab you would probably see 1532 for an ecplicit overhead of 18 (as tc stab does not take the already accounted for header into account so if you request 18 on an ethernet interface you will effectively get 18+14 = 32.) It really is a great feature of cake to undo the kernel's automagic length adjustment so that one can request overhead on top of the ethernet payload/the IP packets.
>
> Best Regards
> Sebastian
>
>> Thanks again =)
>>
next prev parent reply other threads:[~2017-09-07 7:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 2:46 Dennis Fedtke
2017-09-05 3:26 ` Ryan Mounce
2017-09-05 3:37 ` Ryan Mounce
2017-09-05 6:00 ` Dennis Fedtke
2017-09-05 6:49 ` Ryan Mounce
2017-09-05 6:58 ` Jonathan Morton
2017-09-05 20:19 ` Dennis Fedtke
2017-09-06 1:45 ` Ryan Mounce
2017-09-06 7:26 ` Sebastian Moeller
2017-09-07 4:11 ` Dennis Fedtke
2017-09-07 4:18 ` Dennis Fedtke
2017-09-07 4:25 ` Jonathan Morton
2017-09-07 7:41 ` Dennis Fedtke
2017-09-07 7:58 ` Sebastian Moeller
2017-09-07 7:47 ` Sebastian Moeller
2017-09-07 7:58 ` Dennis Fedtke [this message]
2017-09-07 8:07 ` Sebastian Moeller
2017-09-06 7:22 ` Sebastian Moeller
2017-09-05 8:01 ` Sebastian Moeller
2017-09-05 8:35 ` Kevin Darbyshire-Bryant
2017-09-05 8:58 ` Sebastian Moeller
2017-09-05 14:37 ` Ryan Mounce
2017-09-05 15:06 ` Sebastian Moeller
2017-09-05 15:33 ` 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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84ff1b59-ec93-5862-c5e4-d03b50483961@gmail.com \
--to=dennisfedtke@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
/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