From: Dave Taht <dave.taht@gmail.com>
To: starlink@lists.bufferbloat.net
Cc: Matt Mathis <mattmathis@google.com>
Subject: [Starlink] congestion control info off the datapath
Date: Sat, 24 Jul 2021 10:02:43 -0700 [thread overview]
Message-ID: <CAA93jw6FKvw-A8nH8Py5Np-dnt+NJ=gN0oYGBYoYTrXF3PLXKQ@mail.gmail.com> (raw)
One of our newer members is one of the authors of this:
https://people.cs.rutgers.edu/~sn624/papers/ccp-sigcomm18.pdf
I will reserve comment for now. I don't grok the intersection with ebpf as yet.
Please? newer folk here, please briefly introduce yourselves and your
interests in starlink's stuff?
I very much approve of lurkers - even aliases! for those that cannot
talk due to various NDAs, etc, but...
For those here that don't know me already, well, I'm this renegade
that has long lived
outside of the vogon-industrial-military-academic complex with more
key open source
networking contributions to the world than most. These days I'm best
known for the bufferbloat
project and multiple congestion control algorithms/packet schedulers and AQMs
( Please put a copy of https://bufferbloat-and-beyond.net/ in your
reading queue)
but I have a long history going back to 1982 of kicking the tires of
the internet,
creating a RUD, and then fixing it.
My own personal mission (as per the podcast) is to merely see starlink
get sch_cake up on outbound
on the dishy but long term I care a lot about just about anything
networked and in
space from here out to the edges fo the solar system. I'm really low
on spare time
at the moment personally, but if newer folk here would like to
introduce themselves
and point a link at a key paper of theirs or at their work in
progress, perhaps the
conversation will get rolling a bit more. We're still looking for more
folkable to do
our measurement suite in particular.
(we also need to put up the mailing list archive so far for new folk.
Am short an
mailman expert for that if anyone has those chops?)
--
Fixing Starlink's Latencies: https://www.youtube.com/watch?v=c9gLo6Xrwgw
Dave Täht CTO, TekLibre, LLC
next reply other threads:[~2021-07-24 17:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-24 17:02 Dave Taht [this message]
2021-07-26 5:26 ` Ulrich Speidel
2021-07-28 21:00 ` Andrew Crane
2021-07-29 21:31 ` Michael Richardson
2021-07-29 14:57 ` Jared Mauch
2021-07-31 13:04 ` Srinivas Narayana
2021-08-11 17:59 ` Nick Buraglio
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='CAA93jw6FKvw-A8nH8Py5Np-dnt+NJ=gN0oYGBYoYTrXF3PLXKQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=mattmathis@google.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