From: Dennis Fedtke <dennisfedtke@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>, Ryan Mounce <ryan@mounce.com.au>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] overhead and mpu
Date: Thu, 7 Sep 2017 06:11:19 +0200 [thread overview]
Message-ID: <6581a265-041e-5ac0-9d1c-66067e45bfa6@gmail.com> (raw)
In-Reply-To: <0D998858-A2FD-4CE3-8B9B-07C6448C8F3B@gmx.de>
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?
Why is there overhead18 + via-ethernet showing for ingress?
Thanks again =)
next prev parent reply other threads:[~2017-09-07 4:11 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 [this message]
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
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=6581a265-041e-5ac0-9d1c-66067e45bfa6@gmail.com \
--to=dennisfedtke@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--cc=ryan@mounce.com.au \
/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