From: Sebastian Moeller <moeller0@gmx.de>
To: Michael Richardson <mcr@sandelman.ca>
Cc: "Dave Täht" <dave.taht@gmail.com>,
"starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink hidden buffers
Date: Wed, 24 May 2023 20:45:53 +0200 [thread overview]
Message-ID: <E9CD7D6C-FB48-41D9-9917-ADDC0FF9F540@gmx.de> (raw)
In-Reply-To: <2933754.1684953035@dyas>
Hi Michael,
> On May 24, 2023, at 20:30, Michael Richardson via Starlink <starlink@lists.bufferbloat.net> wrote:
>
>
> Dave Taht <dave.taht@gmail.com> wrote:
>>> Could fq_codel emit flow statistics as a side-effect of it's
>>> classifications?
>
>> It does. It always has. "tc -s class show" gives details of each queue.
>
> Good.
> Just a question of hooking up luci to that.
Keep in mind by default fq_codel uses 1024 hash bins, so worst case your GUI needs to display quite a lot of units; on the other hand many flows are really short, and the "tc -s class show" has little "hysteresis" that is once a hash bin runs empty, fq_codel will not report data for that bin. (Which is fine as empty buckets tend to be not very informative, but when using this output to feed a display tool now your sampling/query rate might be too coarse and not show ephemeral buckets).
>
>> There are some really cool things you can do at high sample rates.
>> Here is a live/realtime movie of what netflix actually looks like:
>> https://www.youtube.com/watch?v=C-2oSBr2200 (also) Another thing is
>
> A movie about people watching movies :-)
And a "silent move" at that, very meta and very old school ;)
> I wonder about the privacy implications of doing this at an ISP.
I think keeping the full 5-tuple input to the hash function might be problematic, but "reducing" that to the 10bit bucket-ID should be lossy enough, no?
Regards
Sebastian
P.S.: for cake luci statistics has grown a module that plots the outputs of `tc -s qdisc` for cake instances over time. Sure that is not the per-flow or per hash-bin resolution, but for quickly seeing whether there is on-going high level marking/dropping it should suffice...
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2023-05-24 18:45 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-13 10:10 Ulrich Speidel
2023-05-13 11:20 ` Sebastian Moeller
2023-05-13 12:16 ` Ulrich Speidel
2023-05-13 23:00 ` David Lang
2023-05-13 22:57 ` David Lang
2023-05-14 6:06 ` Ulrich Speidel
2023-05-14 6:55 ` David Lang
2023-05-14 8:43 ` Ulrich Speidel
2023-05-14 9:00 ` David Lang
2023-05-15 2:41 ` Ulrich Speidel
2023-05-15 3:33 ` David Lang
2023-05-15 6:36 ` Sebastian Moeller
2023-05-15 11:07 ` David Lang
2023-05-24 12:55 ` Ulrich Speidel
2023-05-24 13:44 ` Dave Taht
2023-05-24 14:05 ` David Lang
2023-05-24 14:49 ` Michael Richardson
2023-05-24 15:09 ` Dave Collier-Brown
2023-05-24 15:31 ` Dave Taht
2023-05-24 18:30 ` Michael Richardson
2023-05-24 18:45 ` Sebastian Moeller [this message]
2023-05-24 13:59 ` David Lang
2023-05-24 22:39 ` Ulrich Speidel
2023-05-25 0:06 ` David Lang
2023-07-27 20:37 ` Ulrich Speidel
2023-05-24 15:18 ` Mark Handley
2023-05-24 21:50 ` Ulrich Speidel
2023-05-25 0:17 ` David Lang
2023-05-14 9:06 ` Sebastian Moeller
2023-05-14 9:13 ` David Lang
2023-05-14 9:57 ` Oleg Kutkov
2023-05-14 9:59 ` Oleg Kutkov
2023-05-24 15:26 ` Bjørn Ivar Teigen
2023-05-24 21:53 ` Ulrich Speidel
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E9CD7D6C-FB48-41D9-9917-ADDC0FF9F540@gmx.de \
--to=moeller0@gmx.de \
--cc=dave.taht@gmail.com \
--cc=mcr@sandelman.ca \
--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