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>,
	Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
	"Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: [Starlink] "Hunting Heisenbugs" talk Nov 14th 2:30 PM EST
Date: Mon, 13 Nov 2023 15:41:14 -0500	[thread overview]
Message-ID: <CAA93jw6BOvaMNsf7LhdkNqrqoBKMiuambHQ7aKPFRt1ShipFgA@mail.gmail.com> (raw)

Paul McKenney, inventor of Stochastic Fair Queueing (SFQ), inventor of
RCU, solver of million year problems at IBM and now meta, and all
around good speaker, is giving a talk on "Hunting Heisenbugs" 2:30PM
EST Tuesday November 14th, 2023, at the Linux Plumbers conference.

https://lpc.events/event/17/contributions/1504/

A heisenbug is a bug that when you instrument the code to find it,
vanishes. See wikipedia for more details.

I have spent many months, and years, even - trying to turn heisenbugs
into "Bohrbugs". Bufferbloat was, originally, essentially a heisenbug,
until Tom Herbert invented BQL. Every engineer has a few in their
backlog that keeps them awake at night. I have 3 outstanding, the
biggest: I have been trying (in my spare time) for nearly a year now,
trying to find a bug in the mt76's mu-mimo stack that causes excessive
retransmits and latency under circumstances I can rarely replicate,
which is proving more elusive to find as the infamous fq-crypto bug we
had had that stalled make-wifi-fast project out for 4 horrible months,
and stumped dozens of people. It is similarly damaging for users of
that chipset, when it happens.

https://blog.cerowrt.org/post/crypto_fq_bug/

-- 
:( My old R&D campus is up for sale: https://tinyurl.com/yurtlab
Dave Täht CSO, LibreQos

                 reply	other threads:[~2023-11-13 20:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAA93jw6BOvaMNsf7LhdkNqrqoBKMiuambHQ7aKPFRt1ShipFgA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=nnagain@lists.bufferbloat.net \
    --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