From: Pete Heist <peteheist@gmail.com>
To: Dave Taht <dave@taht.net>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake upstream Planning
Date: Wed, 15 Nov 2017 21:44:32 +0100 [thread overview]
Message-ID: <471AD4D9-4007-40BC-9115-821AFD342BA8@gmail.com> (raw)
In-Reply-To: <87375f71h3.fsf@nemesis.taht.net>
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
> On Nov 15, 2017, at 9:04 PM, Dave Taht <dave@taht.net> wrote:
>
> Dave Taht <dave@taht.net <mailto:dave@taht.net>> writes:
>
>>> TCP RTT ~= 8ms with default qdisc, throughput ~= 940 Mbit
>>> TCP RTT ~= 4.5ms with ‘cake unlimited’, throughput ~= 920 Mbit
>>> TCP RTT ~= 1ms with ‘cake unlimited lan’, throughput ~= 920 Mbit
>
> This was with BQL in play? Monitoring BQL's behavior might help.
>
> I'd also love to know an exact setting for the shaper as a close as
> possible to the underlying bandwidth of ethernet. However, I tend to be
> plagued with
Yes, with BQL (Intel I210 with igb driver on the APU2). An rrul_be test with —socket-stats.
[-- Attachment #2: Type: text/html, Size: 5925 bytes --]
next prev parent reply other threads:[~2017-11-15 20:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.7.1510506001.13084.cake@lists.bufferbloat.net>
2017-11-14 9:51 ` [Cake] Donation Pete Heist
2017-11-14 20:10 ` Dave Taht
2017-11-15 14:41 ` Pete Heist
2017-11-15 19:44 ` [Cake] Cake upstream Planning Dave Taht
2017-11-15 20:04 ` Dave Taht
2017-11-15 20:44 ` Pete Heist [this message]
2017-11-15 20:49 ` Dave Taht
2017-11-15 20:06 ` Pete Heist
2017-11-15 20:19 ` Dave Taht
2017-11-15 20:28 ` Nils Andreas Svee
2017-11-15 20:58 ` Pete Heist
2017-11-15 22:40 ` Nils Andreas Svee
2017-11-16 8:41 ` Pete Heist
[not found] <mailman.1019.1510802012.3609.cake@lists.bufferbloat.net>
2017-11-16 9:14 ` Pete Heist
2017-11-16 16:31 ` Dave Taht
2017-11-16 18:40 ` Pete Heist
2017-11-16 19:13 ` Dave Taht
[not found] <mailman.1013.1510778675.3609.cake@lists.bufferbloat.net>
2017-11-16 9:50 ` Pete Heist
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=471AD4D9-4007-40BC-9115-821AFD342BA8@gmail.com \
--to=peteheist@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave@taht.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