From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>, codel@lists.bufferbloat.net
Subject: [Codel] slow start: small chunks can talk
Date: Mon, 31 Jul 2023 15:36:03 -0700 [thread overview]
Message-ID: <CAA93jw4qCJc+vpFB9O5zzG0z8RWFFwS-154-KOCSKpZcusNhCg@mail.gmail.com> (raw)
Promising approach:
https://ieeexplore.ieee.org/document/10188775
--
Podcast: https://www.youtube.com/watch?v=bxmoBr4cBKg
Dave Täht CSO, LibreQos
next reply other threads:[~2023-07-31 22:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 22:36 Dave Taht [this message]
[not found] ` <507f856e-486c-87ff-79a3-50eb47683557@uni-tuebingen.de>
2023-08-01 7:51 ` [Codel] [Bloat] Another passive bandwidth estimation method Sebastian Moeller
[not found] ` <4a158f4f-4f96-44bf-8b08-6f84b0d660df@uni-tuebingen.de>
2023-08-01 8:37 ` Dave Taht
[not found] ` <6392cb1d-92e5-f289-c684-5850bf87df4a@kit.edu>
2023-08-07 10:18 ` [Codel] [Bloat] slow start: small chunks can talk Sebastian Moeller
2023-08-07 16:34 ` Dave Taht
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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4qCJc+vpFB9O5zzG0z8RWFFwS-154-KOCSKpZcusNhCg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=codel@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