From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: Cake List <cake@lists.bufferbloat.net>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>,
Jeremy Austin via Rpm <rpm@lists.bufferbloat.net>,
libreqos <libreqos@lists.bufferbloat.net>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: [Cake] Bufferbloat talks at WLPC Prague 2026 [slides and recordings]
Date: Mon, 26 Oct 2026 15:45:40 +0100 [thread overview]
Message-ID: <CAJUtOOjuZOuYmGJxxCe2PZeU7hO=hQB7i-zG1qawnUJrgNsaMA@mail.gmail.com> (raw)
Hello to all,
Seeing 2 bufferbloat talks at WLPC event, after years of my heckling
(sic!), kicking and screaming, I'm please to report that there were, in
fact, two, nice talks on bufferbloat at Wireless LAN Professional
Conference here in Prague this year.
First one was delivered by Falk Bachman: *Bandwidth Is a Red Herring: Why
Latency Breaks Collaboration in Wi-Fi Networks, Even with Wi-Fi 7
<https://www.thewlpc.com/presentations/bandwidth-is-a-red-herring-why-latency-breaks-collaboration-in-wi-fi-networks-even-with-wi-fi-7-prg-26>
* and
it made my very happy, because Falk was literally the very first person
from the WLPC community that started to listen to my constant b!tching
about this topic.
The other talk has L4S flavor and was delivered by Troy Martin: *"Your
Wi-Fi Is Fast. So Why Does It Feel Slow?" Understanding L4S and the End of
Bufferbloat.
<https://www.thewlpc.com/presentations/your-wi-fi-is-fast-so-why-does-it-feel-slow-understanding-l4s-and-the-end-of-bufferbloat-prg-26>*
Enjoy!
PS: This year's event was really excellent, so I would recommend you to
take a look on the rest of the talks
<https://www.thewlpc.com/conferences/prg26> as well.
All the best,
Frank
Frantisek (Frank) Borsik
*In loving memory of Dave Täht: *1965-2025
https://libreqos.io/2025/04/01/in-loving-memory-of-dave/
https://www.linkedin.com/in/frantisekborsik
Signal, Telegram, WhatsApp: +421919416714
iMessage, mobile: +420775230885
Skype: casioa5302ca
frantisek.borsik@gmail.com
reply other threads:[~2026-10-26 14:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJUtOOjuZOuYmGJxxCe2PZeU7hO=hQB7i-zG1qawnUJrgNsaMA@mail.gmail.com' \
--to=frantisek.borsik@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=libreqos@lists.bufferbloat.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=rpm@lists.bufferbloat.net \
--cc=starlink@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