From: Andy Furniss <adf.lists@gmail.com>
To: David Lang <david@lang.hm>, xnor <xnoreq@gmail.com>
Cc: Cake@lists.bufferbloat.net
Subject: Re: [Cake] cake default target is too low for bbr?
Date: Fri, 28 Apr 2017 22:54:03 +0100 [thread overview]
Message-ID: <2bebaf69-a80a-9aa0-90b3-515686191d6a@gmail.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1704281423080.8252@qynat-yncgbc>
David Lang wrote:
> On Fri, 28 Apr 2017, xnor wrote:
>
>> As I understand it, increase in RTT due to queueing of packets is
>> the main feedback mechanism for BBR. So dropping packets, which I
>> already consider harmful, is really harmful with BBR because
>> you're not telling the sender to slow down.
>
> If BBR does not slow down when packets are dropped, it's too hostile
> to use on a public network. The only way for a public network to
> respond to a flood of traffic higher than what it can handle is to
> drop packets (with a possible warning via ECN shortly before packets
> get dropped). If BBR doesn't slow down, it's just going to be
> wasting bandwidth.
>
>> Instead, with a controlled delay qdisc like cake or codel, you're
>> telling the sender to keep sending the data faster because the
>> qdisc keeps the increase in RTT minimal. To make things worse,
>> you're throwing away perfectly good packets with no effect other
>> than wasting bandwidth.
>
> you are mistaking how cake and codel work. They are working at the
> link endpoint adjacent to where the bandwidth is most limited. They
> drop packets before they get send over the most contrained link. The
> fact that the packets eat up some bandwidth on the non-constrained
> link prior to the bottleneck doesn't matter, the bandwidth is
> available by definition (otherwise it would be a constrained link to
> the endpoint before it)
Well cake may be used on ingress, OK so that is a "hack" but it's better
than nothing. The ingress parameter does help a bit - but not much.
Reducing bufferbloat is a good ideal, but it seems sometimes being too
aggressive can hurt (I've also needed to increase rtt somewhat higher
than the actual latency to get upstream tests to fill bandwidth).
If target is supposed to work 5-10% of rtt value, then maybe cake could
let users choose 10% rather than hard code 5% - to avoid the need to set
excessive rtt values just to raise target.
next prev parent reply other threads:[~2017-04-28 21:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.435.1493406198.3609.cake@lists.bufferbloat.net>
2017-04-28 21:11 ` xnor
2017-04-28 21:29 ` David Lang
2017-04-28 21:54 ` Andy Furniss [this message]
2017-04-28 22:02 ` xnor
2017-04-28 22:26 ` Andy Furniss
2017-04-28 23:52 ` Andy Furniss
2017-04-28 23:54 ` Andy Furniss
2017-05-03 9:50 ` Andy Furniss
2017-05-04 2:13 ` Jim Gettys
2017-05-04 10:22 ` Andy Furniss
2017-05-04 17:40 ` Jim Gettys
2017-05-08 10:37 ` Andy Furniss
2017-04-29 4:32 ` Jonathan Morton
2017-04-29 10:31 ` Andy Furniss
2017-04-28 19:03 Andy Furniss
2017-04-28 20:45 ` [Cake] " Andy Furniss
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=2bebaf69-a80a-9aa0-90b3-515686191d6a@gmail.com \
--to=adf.lists@gmail.com \
--cc=Cake@lists.bufferbloat.net \
--cc=david@lang.hm \
--cc=xnoreq@gmail.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