Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] mems optical switching
Date: Sun, 19 Mar 2023 13:58:52 +0100	[thread overview]
Message-ID: <2892973.1679230732@dyas> (raw)
In-Reply-To: <CAA93jw6YnEGmDfRVFBgeigaJ5bLsdLgXEj-2RtgNsSqjCcfOwQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 690 bytes --]


Dave Taht via Starlink <starlink@lists.bufferbloat.net> wrote:
    > I think, in general, we have gathered here quite a few folk that are
    > interested in new technology, and the list
    > does veer away from starlink issues more often than not. Today, this
    > about google's mems switching tech hit,
    > and I keep wondering where else it could be applied.

    > https://www.semianalysis.com/p/google-apollo-the-3-billion-game

An interesting read.
Starlink content: could they avoid latency and power consumption by using
optical switching in the satellites.  I suspect it's irrelevant, because the
satellites don't have more than about four lasers.  (I think I heard four)




[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2023-03-19 12:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-18 22:19 Dave Taht
2023-03-19 12:58 ` Michael Richardson [this message]
2023-03-19 14:16 ` Brandon Butterworth
2023-03-19 14:33   ` Christian von der Ropp
2023-03-20 11:32     ` Dave Taht
2023-03-20 11:42       ` David Lang
2023-03-20 11:46       ` Mike Puchol
2023-03-20 18:55         ` Ulrich Speidel

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=2892973.1679230732@dyas \
    --to=mcr@sandelman.ca \
    --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