From: Dave Taht <dave.taht@gmail.com>
To: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] a couple quick test runs of the v17+1 patchset
Date: Wed, 30 May 2018 13:53:44 -0700 [thread overview]
Message-ID: <CAA93jw6o42Nn90qb1skPBaGcQ+PiVw0K55JdfxK6sZ9wDiGfqQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4VYWacQLJxSmMgb6U9E5gerYM+ZMj8kLbUgtDeKr2aow@mail.gmail.com>
And I was being an idiot. Using the ethernet keyword to account for
the framing overhead AND shaping to 1Gbit,
I got local latency results twice as good as what I can get from
sch_fq, no muss, no fuss, and no loss of bandwidth vs the unshaped
mode.
Hardware flow control will still defeat us, but....
Summary of rrul test run 'v17-cake-1gbit-ethernet' (at 2018-05-30
20:48:14.853980):
avg median # data pts
Ping (ms) ICMP : 1.74 1.88 ms 347
Ping (ms) UDP BE : 879.31 2.21 ms 349
Ping (ms) UDP BK : 853.93 2.25 ms 349
Ping (ms) UDP EF : 879.93 2.21 ms 349
Ping (ms) avg : 653.73 2.13 ms 350
TCP download BE : 230.61 230.58 Mbits/s 299
TCP download BK : 230.81 230.70 Mbits/s 299
TCP download CS5 : 230.61 230.66 Mbits/s 299
TCP download EF : 230.21 230.58 Mbits/s 299
TCP download avg : 230.56 230.62 Mbits/s 300
TCP download sum : 922.24 922.48 Mbits/s 300
TCP totals : 1858.68 1859.31 Mbits/s 300
TCP upload BE : 322.47 322.56 Mbits/s 290
TCP upload BK : 57.57 57.47 Mbits/s 271
TCP upload CS5 : 322.39 322.49 Mbits/s 276
TCP upload EF : 234.01 234.18 Mbits/s 281
TCP upload avg : 234.11 234.18 Mbits/s 300
TCP upload sum : 936.44 936.72 Mbits/s 300
but the capacity estimate is still 970?
qdisc cake 8017: root refcnt 2 bandwidth 1Gbit diffserv3
triple-isolate split-gso rtt 100.0ms noatm overhead 38 mpu 84
Sent 51504294511 bytes 37724591 pkt (dropped 6, overlimits 64958695
requeues 12)
backlog 0b 0p requeues 12
memory used: 1053008b of 15140Kb
capacity estimate: 970Mbit
min/max network layer size: 28 / 1500
min/max overhead-adjusted size: 84 / 1538
average network hdr offset: 14
Bulk Best Effort Voice
thresh 62500Kbit 1Gbit 250Mbit
target 5.0ms 5.0ms 5.0ms
interval 100.0ms 100.0ms 100.0ms
pk_delay 5us 5us 6us
av_delay 3us 2us 2us
sp_delay 2us 1us 1us
backlog 0b 0b 0b
pkts 3164050 25030267 9530280
bytes 3227519915 35396974782 12879808898
way_inds 0 8 0
way_miss 21 366 25
way_cols 0 0 0
drops 5 0 1
marks 0 0 0
ack_drop 0 0 0
sp_flows 1 3 0
bk_flows 0 1 1
un_flows 0 0 0
max_len 68130 68130 68130
prev parent reply other threads:[~2018-05-30 20:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 20:39 Dave Taht
2018-05-30 20:53 ` Dave Taht [this message]
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=CAA93jw6o42Nn90qb1skPBaGcQ+PiVw0K55JdfxK6sZ9wDiGfqQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.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