From: Stuart Cheshire <cheshire@apple.com>
To: Neal Cardwell <ncardwell@google.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
Frantisek Borsik <frantisek.borsik@gmail.com>,
"Mohit P. Tahiliani" <tahiliani@nitk.edu.in>
Subject: [Bloat] Re: The hell has frozen: Latency mentioned at APNIC 62, during a keynote!
Date: Thu, 17 Sep 2026 17:16:07 -0700 [thread overview]
Message-ID: <DC754C51-8568-4B33-95C4-A29A15635A44@apple.com> (raw)
In-Reply-To: <CADVnQymA2wecUz5t3=56iuU6UjurY_V_iw90agtB2bXF-_JprA@mail.gmail.com>
On Sep 17, 2026, at 12:56, Neal Cardwell <ncardwell@google.com> wrote:
> Likewise, I would not call latency a "resource". The link is the resource. Latency is a performance characteristic. Effective management of the resource (with L4S or other schemes) can yield both low latency and high throughput.
>
> Calling latency a "resource" makes it sound like something that can be built or purchased. One cannot build or purchase low latency. You can purchase hardware that allows low latency, but you still have to deploy protocols that know how to use the signals to achieve low latency and high throughput.
Very good point. This is 100% right.
A “resource” is something that exists in finite quantity, so you need to decide where to allocate that limited resource. Almost by definition, I think calling something a “resource” is synonymous with saying that its allocation is a zero-sum game.
Stuart Cheshire
next prev parent reply other threads:[~2026-09-18 0:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 17:37 [Bloat] The hell has frozen: Latency mentioned at APNIC 62, during a keynote! Frantisek Borsik
2026-09-17 18:24 ` [Bloat] " Stuart Cheshire
2026-09-17 19:56 ` Neal Cardwell
2026-09-17 21:14 ` Richard Scheffenegger
2026-09-18 0:16 ` Stuart Cheshire [this message]
[not found] <178969057349.1938.14005152589460246388@gauss>
2026-09-18 12:11 ` Rich Brown
2026-09-18 21:41 ` bob.mcmahon
2026-09-19 10:03 ` 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=DC754C51-8568-4B33-95C4-A29A15635A44@apple.com \
--to=cheshire@apple.com \
--cc=bloat@lists.bufferbloat.net \
--cc=frantisek.borsik@gmail.com \
--cc=ncardwell@google.com \
--cc=tahiliani@nitk.edu.in \
/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