From: Jonathan Morton <chromatix99@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: Sebastian Moeller <moeller0@gmx.de>,
Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Why are target & interval increased on the reduced bandwidth tins?
Date: Thu, 25 Jun 2020 23:42:31 +0300 [thread overview]
Message-ID: <43093AB9-1B67-487D-B9E1-D52B6D5F5821@gmail.com> (raw)
In-Reply-To: <FBCBE043-450D-4512-85B6-587F8876C7DB@darbyshire-bryant.me.uk>
> On 25 Jun, 2020, at 4:40 pm, Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:
>
> So the scenario I have in my head says that BK traffic could burst at full bandwidth rate (or higher) filling upstream ISP buffers and thus inducing delays on all other traffic because "we think it’s a slow link and have high interval and target values” delaying our response to the burst. Whereas if we retain the default interval & target from the true link capacity calculation we’ll jump on it in time.
You might be forgetting about ack clocking. This gives the sender information about how quickly data is reaching the receiver, and normally the sender will generate either one or two packets for each packet acked. So even without an immediate AQM action, there is still *some* restraint on the sender's behaviour within approximately one RTT.
This is one of the many subtle factors that Codel relies on.
- Jonathan Morton
prev parent reply other threads:[~2020-06-25 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 14:33 Kevin Darbyshire-Bryant
2020-06-24 14:40 ` Sebastian Moeller
2020-06-25 13:40 ` Kevin Darbyshire-Bryant
2020-06-25 20:42 ` Jonathan Morton [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=43093AB9-1B67-487D-B9E1-D52B6D5F5821@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=kevin@darbyshire-bryant.me.uk \
--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