From: Dave Taht <davet@teklibre.net>
To: Doc Searls <doc@searls.com>
Cc: Dave Taht <dave.taht@gmail.com>, starlink@lists.bufferbloat.net
Subject: [Starlink] Q
Date: Wed, 23 Jun 2021 11:18:48 -0700 [thread overview]
Message-ID: <C5180DCD-4475-4DA3-8348-AE95A51C2464@teklibre.net> (raw)
In-Reply-To: <3770C0CE-88EB-46D4-88ED-ADE09E247D37@searls.com>
[-- Attachment #1: Type: text/plain, Size: 4823 bytes --]
dear doc:
great article, thx, he’s already most of the way to the right page. Can you introduce us off list?
one hope is we do failover better using the mwan3 tool in openwrt instead of relying on ping but the supplied statistics.
Another is to get the starwrt codebase up on the supplied router. We already have plenty of qcom IPQ8014 routers under test in openwrt mainline, which is the chipset the starlink router is based on….
… but most of our new work had shifted over the mt76 chipsets and the higher end armada platfoems and there are three large things involving aql, wifi retries, and cake left to make work on the ath10k derived stuff that I’d hoped would make the final build...
public work over here stopped a while back, but we can resume.
https://forum.openwrt.org/t/aql-and-the-ath10k-is-lovely/59002
> On Jun 22, 2021, at 6:20 PM, Doc Searls <doc@searls.com> wrote:
>
> When you come on FLOSS Weekly, Jonathan here will be my co-host:
>
> https://hackaday.com/2021/05/24/starlink-a-review-and-some-hacks/ <https://hackaday.com/2021/05/24/starlink-a-review-and-some-hacks/>
>
> Never mind that he doesn't know about bufferbloat on Starlink. He'll get it. And he's a great dude. You should loop him in. He can be helpful. So can his minions.
>
> Doc
>
>> On Jun 21, 2021, at 11:56 AM, Dave Taht <dave.taht@gmail.com <mailto:dave.taht@gmail.com>> wrote:
>>
>> On Mon, Jun 21, 2021 at 8:47 AM Dave Taht <dave.taht@gmail.com <mailto:dave.taht@gmail.com>> wrote:
>>>
>>> On Mon, Jun 21, 2021 at 8:06 AM Michael Richardson <mcr@sandelman.ca <mailto:mcr@sandelman.ca>> wrote:
>>>>
>>>> Dave Taht <dave.taht@gmail.com <mailto:dave.taht@gmail.com>> wrote:
>>>>> It came up recently that a lot of folk don't like the idea of dropping
>>>>> packets as a congestion
>>>>> control mechanism. Like loss or not... the fundamental paper on this
>>>>> subject is Van Jacobson and Mike Karels:
>>>>
>>>>> "On congestion avoidance and control"
>>>>
>>>>> http://web.stanford.edu/class/cs244/papers/CongestionControl.pdf <http://web.stanford.edu/class/cs244/papers/CongestionControl.pdf>
>>>>
>>>> I saved this post a long time ago.
>>>> http://www.sandelman.ca/mcr/humour/vanj-enet-posting.txt <http://www.sandelman.ca/mcr/humour/vanj-enet-posting.txt>
>>
>> From that piece:
>>
>> "funding agents looking for high speed,
>> next-generation networks may forget that research to make slow
>> things go fast sometimes makes fast things go faster".
>>
>> Recently I dusted off fq_codel_fast in light of the cache misses
>> finally showing up
>> in a 100gbit dual bonded scenario over here:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=848ca9182a7d25bb54955c3aab9a3a2742bf9678 <https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=848ca9182a7d25bb54955c3aab9a3a2742bf9678>
>>
>> asked the author to give it a try.
>>
>>
>>
>>
>>
>>> That was a *great* piece of history thx. And he referenced greg
>>> chesson's work on XTP,
>>> ( https://grainger.illinois.edu/alumni/distinguished/9560 <https://grainger.illinois.edu/alumni/distinguished/9560> )
>>>
>>> Greg was an early consultant to the bufferbloat project...
>>> he sadly passed before we ever had a chance to jam together.
>>>
>>> https://news.ycombinator.com/item?id=9795462 <https://news.ycombinator.com/item?id=9795462>
>>>
>>>> There is another one about how he crashed Interop, which I don't know where I
>>>> put.
>>>
>>> More folk should have seen van's codel preso at ietf 84. It was the
>>> very very early days of webrtc.
>>>
>>> https://archive.org/details/video1_20191129
>>>>
>>>> --
>>>> ] Never tell me the odds! | ipv6 mesh networks [
>>>> ] Michael Richardson, Sandelman Software Works | IoT architect [
>>>> ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Latest Podcast:
>>> https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/
>>>
>>> Dave Täht CTO, TekLibre, LLC
>>
>>
>>
>> --
>> Latest Podcast:
>> https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/ <https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/>
>>
>> Dave Täht CTO, TekLibre, LLC
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net <mailto:Starlink@lists.bufferbloat.net>
>> https://lists.bufferbloat.net/listinfo/starlink <https://lists.bufferbloat.net/listinfo/starlink>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
[-- Attachment #2: Type: text/html, Size: 25858 bytes --]
prev parent reply other threads:[~2021-06-23 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 8:41 [Starlink] on using and debugging lossless congestion control (RFC3168 ECN) Dave Taht
[not found] ` <20160.1624287984@localhost>
2021-06-21 15:47 ` Dave Taht
2021-06-21 15:56 ` Dave Taht
2021-06-23 1:20 ` Doc Searls
2021-06-23 18:18 ` Dave Taht [this message]
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=C5180DCD-4475-4DA3-8348-AE95A51C2464@teklibre.net \
--to=davet@teklibre.net \
--cc=dave.taht@gmail.com \
--cc=doc@searls.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