From: Aaron Wood <woody77@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] "bullwhip" effect - an analogy that applies to TCP and excessive latency
Date: Sun, 29 Jan 2023 13:16:10 -0800 [thread overview]
Message-ID: <CALQXh-P_LtZYyAaWxTZjtMWuWqBjK0d0rdLVEBR-Ld6JZtNE=A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 246 bytes --]
I read this earlier in the week, and thought it applied well to describing
how excessive latency causes TCP (cubic, reno, etc) overshoot and collapse
in bufferbloat situations:
https://read.fluxcollective.org/i/98919216/lens-of-the-week
-Aaron
[-- Attachment #2: Type: text/html, Size: 390 bytes --]
reply other threads:[~2023-01-29 21:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALQXh-P_LtZYyAaWxTZjtMWuWqBjK0d0rdLVEBR-Ld6JZtNE=A@mail.gmail.com' \
--to=woody77@gmail.com \
--cc=bloat@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