From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] OCLUG talk on bufferbloat
Date: Fri, 3 May 2013 14:20:28 +0200 [thread overview]
Message-ID: <20130503142028.463fd488@redhat.com> (raw)
In-Reply-To: <4739.1367352564@sandelman.ca>
On Tue, 30 Apr 2013 16:09:24 -0400
Michael Richardson <mcr@sandelman.ca> wrote:
> http://oclug.on.ca/meeting/100/
> June Meeting: Too much RAM breaks Internet! News at 7!
>
> I will be stealing liberally, and I'm gonna walk people through the VJ
> water fountain analogy.... I think that I might then repeat it with
> audience participation.... likely take something from Kanban.
Great to hear that others have picked up on preaching Van Jacobsons
water fountain analogy :-)
See my preaching here:
http://youtu.be/BLCd__1mPz8?t=18m28s
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Sr. Network Kernel Developer at Red Hat
Author of http://www.iptv-analyzer.org
LinkedIn: http://www.linkedin.com/in/brouer
prev parent reply other threads:[~2013-05-03 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 20:09 Michael Richardson
2013-05-03 12:20 ` Jesper Dangaard Brouer [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/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=20130503142028.463fd488@redhat.com \
--to=brouer@redhat.com \
--cc=bloat@lists.bufferbloat.net \
--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