From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: galene@lists.galene.org
Subject: [Galene] Re: Future plans: Pion v4 and TWCC
Date: Thu, 2 Jan 2025 09:58:03 -0800 [thread overview]
Message-ID: <CAA93jw6NEkgGHfJTKcYRrrp9+yXrVoHZWdzjZL1s9-ji+ibv9Q@mail.gmail.com> (raw)
In-Reply-To: <875xmy6l46.wl-jch@irif.fr>
On Wed, Jan 1, 2025 at 5:49 PM Juliusz Chroboczek <jch@irif.fr> wrote:
>
> > Did delay and not just loss make it into pion?
>
> To my surprise, I've found what looks like a fairly complete
> implementation of GCC. It remains to be seen how well it works in
> practice.
>
> Dave, interested in collaborating on making some benchmarks?
yes!
>
> -- Juliusz
--
Dave Täht CSO, LibreQos
prev parent reply other threads:[~2025-01-02 17:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 20:45 [Galene] " Juliusz Chroboczek
2025-01-01 22:27 ` [Galene] " Dave Taht
2025-01-02 1:16 ` Sean DuBois
2025-01-02 17:57 ` Dave Taht
2025-01-02 19:15 ` Tim Panton
2025-01-02 1:49 ` Juliusz Chroboczek
2025-01-02 17:58 ` Dave Taht [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.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw6NEkgGHfJTKcYRrrp9+yXrVoHZWdzjZL1s9-ji+ibv9Q@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=galene@lists.galene.org \
--cc=jch@irif.fr \
/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