From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <davet@teklibre.net>
Cc: Nathan Owens <nathan@nathan.io>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] dynamically adjusting cake to starlink
Date: Wed, 9 Jun 2021 12:20:02 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.2106091137570.13354@uplift.swm.pp.se> (raw)
In-Reply-To: <AB233C27-07F0-4D2C-A433-4E6C0D64299A@teklibre.net>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
On Wed, 9 Jun 2021, Dave Taht wrote:
> … and a meeting with some starlink execs at 11AM today.
Nice!
The solution space you're working on ("one device knows its next-hop speed
and adjacent device needs to know this") is applicable to for instance
cable, DSL, PON, wifi etc.
I seem to remember there has been work in BBF to have the BNG know the
sync-up speed of DSL in order to do proper buffering, what you need to do
is to come from "the other end".
Would be nice if there was a generic mechanism for this but since several
of these devices use L2 I think it'd have to be something LLDP like (also
on L2).
Dave, how often does information regarding rate/scheduler need to be
distributed from the scheduling node to the node that is trying to not use
the upstream buffer? I presume this is in the 0.1 to 1s range, because the
scheduler might change quite frequently and substantially?
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2021-06-09 10:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 3:31 [Starlink] pretty cool starlink visualizer Darrell Budic
2021-06-06 4:26 ` David Lang
2021-06-08 21:54 ` Nathan Owens
2021-06-09 9:12 ` [Starlink] dynamically adjusting cake to starlink Dave Taht
2021-06-09 10:20 ` Mikael Abrahamsson [this message]
2021-06-09 16:39 ` Michael Richardson
2021-06-09 18:10 ` David Lang
2021-06-09 12:09 ` Nathan Owens
2021-06-09 12:16 ` Mike Puchol
2021-06-09 13:21 ` Dave Taht
2021-06-09 14:12 ` Michael Richardson
2021-06-09 15:23 ` Mike Puchol
2021-06-09 21:18 ` Michael Richardson
2021-06-09 21:36 ` Nathan Owens
2021-06-09 23:37 ` Mike Puchol
2021-06-09 15:32 ` Nathan Owens
2021-06-09 15:46 ` David Lang
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=alpine.DEB.2.20.2106091137570.13354@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=davet@teklibre.net \
--cc=nathan@nathan.io \
--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