From: Dave Taht <dave.taht@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] google's implementation of aql and fq_codel for wifi
Date: Fri, 2 Jul 2021 13:56:04 -0700 [thread overview]
Message-ID: <CAA93jw4ByjE9jJSrZP9rO1T_cSQ+K_20NEmvuKHD3W2qit7hJQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
It's kind of come to my attention that people rarely click on links
anymore. So the google document attached goes into detail as to how
well google's implementation of aql and fq_codel works on their wifi
products... for the last 5 years or so.
The RvR vs latency plots from page 12 forward are to die for. This is
why I'd wanted a packet capture from jared's test to see if starlink
had missed these two subsystems also in their initial starlink router
implementation.
I also tend to think the flow-queuing scheduling algorithm might help
on the sat links as well, but that would require testing and
simulation.
--
Latest Podcast:
https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/
Dave Täht CTO, TekLibre, LLC
[-- Attachment #2: Airtime based queue limit for FQ_CoDel in wireless interface.pdf --]
[-- Type: application/pdf, Size: 482155 bytes --]
reply other threads:[~2021-07-02 20:56 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/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=CAA93jw4ByjE9jJSrZP9rO1T_cSQ+K_20NEmvuKHD3W2qit7hJQ@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