Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Fwd: async circuits 30+ years later
Date: Sun, 12 Mar 2023 13:17:47 -0700	[thread overview]
Message-ID: <CAA93jw6Rp_VG9NiCksDgSLiRjnzQRuhyueorxjXAb9RaC6kQWw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7fKqGUFUDE0z7dGrmgnDknpZgYo-bDtiOg8mh8Lkk2_A@mail.gmail.com>

I often think, I should never have played with this, I should never
have learned how to think like this about hardware, I am nearly alone
in the world, and completely unable to cope with modern hardware
design tools because of this:

https://authors.library.caltech.edu/43698/1/25YearsAgo.pdf

I am happy to see there is still research ongoing, like I pointed to
in my previous message. I thought (2002?) that the "amulet" async arm
processor was going to sweep the world for wireless-related circuits
because of the low self-noise...

Anyway, the shedding work problem and the unbounded queue problem are
distinctly different problems, thank you for helping me get the two
clear in my head vs language design!


-- 
Come Heckle Mar 6-9 at: https://www.understandinglatency.com/
Dave Täht CEO, TekLibre, LLC

      parent reply	other threads:[~2023-03-12 20:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.7.1678636801.9000.starlink@lists.bufferbloat.net>
2023-03-12 18:51 ` [Starlink] RFC: bufferbloat observability project (Dave Taht) David P. Reed
2023-03-12 18:56   ` David P. Reed
2023-03-12 21:10     ` Sauli Kiviranta
     [not found]   ` <CAA93jw40sExcWj5t1HUHZ7pGCSP7b18quY3aBx4MCfyggvamgw@mail.gmail.com>
     [not found]     ` <CAA93jw7fKqGUFUDE0z7dGrmgnDknpZgYo-bDtiOg8mh8Lkk2_A@mail.gmail.com>
2023-03-12 20:17       ` 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=CAA93jw6Rp_VG9NiCksDgSLiRjnzQRuhyueorxjXAb9RaC6kQWw@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