From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: libreqos <libreqos@lists.bufferbloat.net>
Subject: [LibreQoS] New devblog: Separating Enqueued and Actual Traffic States
Date: Wed, 8 Apr 2026 23:43:16 +0200 [thread overview]
Message-ID: <CAJUtOOibsDEe93Jay6C9y8Drb66BYs2-1UGiywG7wx+pgie-dg@mail.gmail.com> (raw)
For a long time, LibreQoS has only gathered traffic data at “enqueue” time
- when packets enter TC. This has led to LibreQoS’s monitoring occasionally
looking inaccurate - and fails to highlight just how tight the
CAKE/fq_codel + HTB traffic shaping really is. A recent update changed this:
https://devblog.libreqos.com/posts/0014-kprobe/
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-04-08 21:39 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/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJUtOOibsDEe93Jay6C9y8Drb66BYs2-1UGiywG7wx+pgie-dg@mail.gmail.com \
--to=frantisek.borsik@gmail.com \
--cc=libreqos@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