From: Jake Holland <jakeholland.net@gmail.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Quote of the week
Date: Tue, 23 May 2023 23:39:45 -0000 [thread overview]
Message-ID: <CAGac5Agvh6q9cPRFhrWJsc6w3+-scudBfm0J058JNq63Tofb5g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 620 bytes --]
Oh, that brings me back. This is going to be such a fun rollout I can
hardly wait.
Here's to hoping we wind up with fewer regrets about ECT(1) than we started
with, since hope is all I've got left here. All my attempts at comments
have been commented.
Imma go crawl back in bed and pull the covers over my head again.
-Jake
On 05-23, 2:05 PM, "Dave Taht via Bloat" <bloat@lists.bufferbloat.net>
wrote:
from: https://www.ietf.org/blog/banishing-bufferbloat/
"Therefore, innovations like L4S and FQ-CoDel complement each other
and should be deployed together."
[-- Attachment #2: Type: text/html, Size: 2896 bytes --]
next reply other threads:[~2023-05-23 23:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 23:39 Jake Holland [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-23 21:05 Dave Taht
2023-05-24 6:18 ` Sebastian Moeller
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=CAGac5Agvh6q9cPRFhrWJsc6w3+-scudBfm0J058JNq63Tofb5g@mail.gmail.com \
--to=jakeholland.net@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