From: Dave Taht <dave.taht@gmail.com>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] cross layer queue management
Date: Fri, 8 Sep 2023 10:00:06 -0700 [thread overview]
Message-ID: <CAA93jw5sJ6M=g04DT93=YWimzNrZWdUrFu5GvmYEmt21NWvB5Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]
Over here we have been having a great deal of fun speculating about some
increasingly researchy ideas for the cake queuing discipline, and in the
last section, discussing at more length means to cope with the 40ms, 15s
bump (or bang) presently in there while preserving correct behavior of
existing congestion controls. Some great comments are here:
https://docs.google.com/document/d/1tTYBPeaRdCO9AGTGQCpoiuLORQzN_bG3TAkEolJPh28/edit
so many unknowns!
One of the things we learned from the initial teardowns of the dishy was
that it has a ntpd supported GPS chip, which means the dishy could be
supplying really accurate time via ntp or pptp to routers downstream of it.
It would be cool if it did that, but so far as I know, still doesn´t. A
precisely synced router could more smartly buffer and drop packets.
How likely is it for this reconfiguration interval to remain a thing? I´d
hate to burn the time coding up the concept (and slaving a router to
another time sync source - I still have a couple of the 1 pps gps dongles
we built as part of the thumbgps project lying around, more than a few
people here have gps on their raspi hats) only to see it vanish, as much as
I would like it to vanish.
--
Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
Dave Täht CSO, LibreQos
[-- Attachment #2: Type: text/html, Size: 1881 bytes --]
next reply other threads:[~2023-09-08 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 17:00 Dave Taht [this message]
2023-09-08 17:46 ` David Lang
2023-09-08 17:50 ` Dave Taht
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='CAA93jw5sJ6M=g04DT93=YWimzNrZWdUrFu5GvmYEmt21NWvB5Q@mail.gmail.com' \
--to=dave.taht@gmail.com \
--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