From: Kathleen Nichols <nichols@pollere.net>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] RED 13 years later
Date: Sat, 10 Feb 2024 09:38:54 -0800 [thread overview]
Message-ID: <9d6ef700-175c-46c1-987a-9e97333c9b3c@pollere.net> (raw)
In-Reply-To: <526673ff-34dd-49aa-ba1a-7fae47ac5494@sewingwitch.com>
A big issue is that "average queue length" was and is a terrible
indicator of congestion. But I think the first "bug" Van was referring
to was the original RED "control law" - I asked him why he thought it
would work as it really ends up looking like a step function which your
first control theory course will show is rather primitive. The thing is,
that TCP is really robust and almost anything will "work" on long-lived
TCP connections. Which is what everyone used for testing.
On 2/10/24 9:10 AM, Kenneth Porter via Bloat wrote:
> I didn't know what RED was and had to look it up. For others new to the
> lingo:
>
> https://en.wikipedia.org/wiki/Random_early_detection
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
prev parent reply other threads:[~2024-02-10 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-10 4:32 Dave Taht
2024-02-10 17:10 ` Kenneth Porter
2024-02-10 17:38 ` Kathleen Nichols [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/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=9d6ef700-175c-46c1-987a-9e97333c9b3c@pollere.net \
--to=nichols@pollere.net \
--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