From: "David P. Reed" <dpreed@deepplum.com>
To: "Cake List" <cake@lists.bufferbloat.net>
Cc: "bloat" <bloat@lists.bufferbloat.net>, "Dave Taht" <dave.taht@gmail.com>
Subject: [Bloat] Two questions re high speed congestion management and datagram protocols
Date: Sat, 24 Jun 2023 14:41:52 -0400 (EDT) [thread overview]
Message-ID: <1687632112.01524513@apps.rackspace.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]
I was recently looking at congestion control algorithms - endpoint-based ones - that would deal with very low level, very low latency requirements in datacenters that use high speed switch fabrics. (note: congestion control in such datacenters is a very, very real issue, especially since some layer 2 switches are overbuffered by a huge factor, so they don't signal congestion while building very long queues at 40-400 Gb/sec)
I came across this work from MIT CSAIL [ https://ccp-project.github.io/ccp-guide/ ]( https://ccp-project.github.io/ccp-guide/ )
I also was looking back to DCCP as a useful way to get a UDP that handled congestion without engaging the higher layers, and preserving the other flexibility of UDP.
Anyone here have any experience with looking at the performance of these, especially w.r.t. Cake, which operates at the IP layer and thus takes direct advantage of IP congestion signalling? Does libreqos look like it might help?
[as the guy most associated with the creation of UDP, this remains an area of great interest personally, and is also presumably of relevance to QUIC... I don't know if either of these things are supported in systems other than Linux, but in server datacenters and my home lab, Linux networking is all that matters]
- David
[-- Attachment #2: Type: text/html, Size: 2443 bytes --]
next reply other threads:[~2023-06-24 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 18:41 David P. Reed [this message]
2023-06-25 18:51 ` Stephen Hemminger
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=1687632112.01524513@apps.rackspace.com \
--to=dpreed@deepplum.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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