From: Dave Taht <dave.taht@gmail.com>
To: Rpm <rpm@lists.bufferbloat.net>
Subject: [Rpm] in case anyone here digs podcasts
Date: Sun, 19 Feb 2023 15:49:23 -0800 [thread overview]
Message-ID: <CAA93jw66JhMFUJfo50B_kpC2-Og9LpYJUozkPWBABt7_uKGUsg@mail.gmail.com> (raw)
https://packetpushers.net/podcast/heavy-networking-666-improving-quality-of-experience-with-libreqos/
came out yesterday. You'd have to put up with about 8 minutes of my
usual rants before we get into where we are today with the project and
the problems we are facing. (trying to scale past 80Gbit now) We have
at this point validated the behavior of several benchmarks, and are
moving towards more fully emulating various RTTs. See
https://payne.taht.net and click on run bandwidth test to see how we
are moving along. It is so nice to see sawtooths in real time!
Bufferbloat is indeed, the number of the beast.
--
Surveillance Capitalism? Or DIY? Choose:
https://blog.cerowrt.org/post/an_upgrade_in_place/
Dave Täht CEO, TekLibre, LLC
next reply other threads:[~2023-02-19 23:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-19 23:49 Dave Taht [this message]
2023-02-20 15:38 ` Tim Chown
2023-02-20 21:13 ` rjmcmahon
2023-02-21 0:50 ` rjmcmahon
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/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw66JhMFUJfo50B_kpC2-Og9LpYJUozkPWBABt7_uKGUsg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=rpm@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