From: Bob McMahon <bob.mcmahon@broadcom.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: Dave Taht <dave.taht@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [EXTERNAL] Re: Terminology for Laypeople
Date: Thu, 13 May 2021 20:47:36 -0700 [thread overview]
Message-ID: <CAHb6LvrKvD7eomS5fBnKtuphEUO3FWHNR1dVgkYzoQacn8DhEQ@mail.gmail.com> (raw)
In-Reply-To: <28847.1620853812@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 2688 bytes --]
hmm, it seems kinda like the speed of causality
<https://www.sciencealert.com/watch-why-the-speed-of-light-is-not-about-light#:~:text=As%20Matt%20explains%2C%20the%20speed,the%20Universe%2C%20can%20agree%20on.>
applied to computers that share information in order to proceed
Bob
On Wed, May 12, 2021 at 2:10 PM Michael Richardson <mcr@sandelman.ca> wrote:
>
> Dave Taht <dave.taht@gmail.com> wrote:
> > On Wed, May 12, 2021 at 9:02 AM Michael Richardson <mcr@sandelman.ca
> >
> > wrote:
> >>
> >> The part I'd like to simplify is "latency".... Most people can
> >> understand that the hot water tap doesn't produce hot water
> instantly,
> >> but I don't know how leverage that experience to networking
> directly.
> >> Idle and Working are good.
>
> > The demo I did in my broadcom preso ages back was the simplest I
> could
> > imagine, but not on the slides. (
> > http://www.taht.net/~d/broadcom_aug9_2018.pdf )
>
> > I brought a coffee pot, a large carafe, two differently sized
> funnels,
> > an eye dropper, (and a towel!)
>
> Yes, that's a good demonstration for technical people.
> I tried to do this at a LUG with audience involved theatre, but then you
> did
> it better at some Australian event.
>
> But, I'm looking for terminology that I can use with my mother-in-law.
> (She's just signed up with a 802.11 based rural provider for her cottage
> for
> the summer. Made financially feasible only because they'll let her cancel
> for 6 months when it's winter. I'm providing a modem. I suspect that the
> bandwidth is not-constant, so I wonder what I'll tell sql scripts...)
>
> --
> ] Never tell me the odds! | ipv6 mesh
> networks [
> ] Michael Richardson, Sandelman Software Works | IoT
> architect [
> ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on
> rails [
>
>
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
[-- Attachment #1.2: Type: text/html, Size: 3641 bytes --]
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]
next prev parent reply other threads:[~2021-05-14 3:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 13:22 Livingood, Jason
2021-05-12 16:02 ` Michael Richardson
2021-05-12 16:40 ` Dave Taht
2021-05-12 21:10 ` Michael Richardson
2021-05-14 3:47 ` Bob McMahon [this message]
2021-05-16 18:07 ` Jonathan Morton
2021-05-17 21:27 ` Matt Mathis
2021-05-18 0:47 ` Bob McMahon
2021-05-18 6:31 ` Neil Davies
2021-05-18 15:24 ` Matt Mathis
2021-05-18 20:59 ` Bob McMahon
2021-05-18 22:29 ` David Lang
2021-05-19 0:02 ` Bob McMahon
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHb6LvrKvD7eomS5fBnKtuphEUO3FWHNR1dVgkYzoQacn8DhEQ@mail.gmail.com \
--to=bob.mcmahon@broadcom.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=mcr@sandelman.ca \
/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