From: Loganaden Velvindron <loganaden@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] lanman2018 cake talk ideas
Date: Mon, 18 Jun 2018 21:50:25 +0400 [thread overview]
Message-ID: <CAOp4FwRXf0Q9vXS_DEG0jO00PiTvwD6VB-AWbLRiguQE4D0RXw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7B5DJ-jaRF18z6sCLrB9ubCrb2bdnewTBG=ZHVp8FENA@mail.gmail.com>
On Mon, Jun 18, 2018 at 9:44 PM, Dave Taht <dave.taht@gmail.com> wrote:
> I started at the lanman2018 talk (to be given next tuesday), this past
> weekend, for "piece of cake" ( https://arxiv.org/abs/1804.07617 )
>
> Try as I might, finding a memorable narrative hook to fit into 20
> minutes eludes me. There's so much to cake! There's no room for me to
> break out a guitar or carry a case of water bottles into this preso.
>
> A principal complaint of the reviewers of the paper was the lack of
> real world tests, so I snuck in a couple sides for that and am working
> on incorporating the graphs and other text from the paper.
>
> But ya know, it's always been a group effort and if anyone(s) here
> would like to contribute better slides, jokes, text, ideas, graphs,
> charts, or whatever, it would be helpful, because I can no longer see
> the forest after passing through it. I've oft wished we had the
> equivalent of a corp communications department 'cause my attempts at
> graphics generally suck.
>
> What does a ieee lanman2018 audience already grok, what needs to be explained?
>
> I will be periodically updating the currently very raw
>
> http://www.taht.net/~d/cake/ieee.odp
>
> as we go along. Please share your thoughts....
>
>
I thought that BBR solved a number of bufferbloat issues ? Maybe
elaborate on the shortcomings of BBR. Particularly this comment:
"But best case only work within an RTT"
>
>
> --
>
> Dave Täht
> CEO, TekLibre, LLC
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
next prev parent reply other threads:[~2018-06-18 17:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 17:44 Dave Taht
2018-06-18 17:50 ` Loganaden Velvindron [this message]
2018-06-18 17:52 ` Loganaden Velvindron
2018-06-20 8:25 ` Luca Muscariello
2018-06-20 15:45 ` Pete Heist
2018-06-21 3:43 ` Dave Taht
2018-06-21 7:04 ` Pete Heist
2018-06-21 7:55 ` Jonas Mårtensson
2018-06-21 9:42 ` Sebastian Moeller
2018-06-22 7:45 Felix Resch
2018-06-22 8:05 ` Pete Heist
2018-06-23 5:14 ` Dave Taht
2018-06-23 5:35 ` Dave Taht
2018-06-23 7:12 ` Jonathan Morton
2018-06-26 6:58 ` Dave Taht
2018-06-26 8:33 ` Pete Heist
2018-06-26 10:52 ` Toke Høiland-Jørgensen
2018-06-26 13:13 ` Dave Taht
2018-06-26 8:34 ` Sebastian Moeller
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOp4FwRXf0Q9vXS_DEG0jO00PiTvwD6VB-AWbLRiguQE4D0RXw@mail.gmail.com \
--to=loganaden@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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