Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <davet@teklibre.net>
To: starlink@lists.bufferbloat.net
Cc: lk@cs.ucla.edu
Subject: [Starlink] when hackers stay up late and queueing theory 101
Date: Sun, 27 Jun 2021 11:45:19 -0700	[thread overview]
Message-ID: <A254F55D-3785-495B-8DFB-8F30D4600C96@teklibre.net> (raw)

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

One of my most inspirational books over the years the bufferbloat effort has run was “where wizards stay up late”

https://www.amazon.com/Where-Wizards-Stay-Up-Late/dp/0684832674

(several people featured in that book are on this mailing list)

My hero, in the book, was len kleinrock. His gang of grad students at UCLA took great delight in finding new ways to break and improve on the early arpanet.

Their bottom up efforts drove the (otherwise great) engineers driving the code and top down design at BBN absolutely insane, but we got a lot out of the end result.

https://en.wikipedia.org/wiki/Leonard_Kleinrock

Len Kleinrock’s work on queue theory is remarkably accessible to even a college sophomore in business... but seems to be sadly mostly out of print at the moment.

https://www.amazon.com/s?k=Queueing+Systems+Volume+1%3A+Theory+by+Leonard&i=stripbooks&ref=nb_sb_noss

THANKFULLY archive.org has been making his books available here for quite some time: 

https://archive.org/details/queueingsystems01klei

https://archive.org/details/queueingsystems02klei/

Queue theory notation is quite weird and hard to grok. However the more CS oriented Volume 2 is the book I relied upon heavily while developing enhancements to fq_codel and its successors.

I can send along my tattered dog-eared copy to whoever might be willing to read it. If you agree to send it back!







[-- Attachment #2: Type: text/html, Size: 3399 bytes --]

                 reply	other threads:[~2021-06-27 18:45 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=A254F55D-3785-495B-8DFB-8F30D4600C96@teklibre.net \
    --to=davet@teklibre.net \
    --cc=lk@cs.ucla.edu \
    --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