From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Pete Heist <pete@heistp.net>, Dave Taht <dave.taht@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] lanman2018 cake talk ideas
Date: Tue, 26 Jun 2018 12:52:24 +0200 [thread overview]
Message-ID: <87r2ktn7kn.fsf@toke.dk> (raw)
In-Reply-To: <B360FE61-66B6-436D-995A-C4A28D78051A@heistp.net>
Pete Heist <pete@heistp.net> writes:
>> On Jun 26, 2018, at 8:58 AM, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> I got about, I don't know, 5? problematic slides, and it needs to get
>> to 20 by 9AM EDT, it's 3AM and I'm gonna catch some zs.
>>
>> http://www.taht.net/~d/cake/sch_cake_ieee_lanman2018.odp
>>
>> On Fri, Jun 22, 2018 at 10:14 PM, Dave Taht <dave.taht@gmail.com> wrote:
>>> I have to get on the plane tomorrow night at midnight and I've tried
>>> to capture some of your comments and ideas in:
>>>
>>> http://www.taht.net/~d/cake/sch_cake_ieee_lanman2018.odp
>>>
>>> It's in its usual mess at this point - usually I don't share stuff
>>> this raw! but I'm totally open to text suggestions, graphics, etc,
>>> etc, etc - there's the plane flight and more than a few days left to
>>> pound it into shape and after I get a feel for the conference monday
>>> will end up doing another pass before the talk tuesday. What to say on
>>> each slide is helpful (jokes appreciated, a lot of what I've had to
>>> say so far is dripping with sarcasm which I know doesn't translate
>>> well).
>>>
>>> I think focusing on per host fq is probably the strongest point to
>>> develop and I kind of wanted a diagram of a whole bunch
>>> of different host types and graphically illustrating what happens vs
>>> fifo, fq_codel, and cake.
>
> Sorry I’ve been heads down testing / writing. It looks like your challenge is 20 minutes for 3+ decades of info. Quick ideas to compress it:
>
> 1) Merge and reduce slides 9 (The case for per-host fair queueing) and 11 (The need for host and flow fairness)
> 2) Slide 14 (comparable to htb+fq_codel) could probably go? doesn’t sell compared to other stuff
> 3) Merge and reduce slides 17 (Deficit based shaping) and 18 (Achieving near perfect utilization) and reduce content
> 4) During the presentation, go through slides 1-8 quickly, but without
> dismissiveness
+1 to all of these. Possibly also nuke slide 13 (or move it to 'extra
slides'). The setup commands are not going to mean anything to those in
the audience (I'm guessing that would be most of the audience) who are
not familiar with Linux/TC.
> On the plus side, I think it’s good you re-focused this on fair
> queueing for this audience. Nice work.
Yeah, I agree. Very nice :)
-Toke
next prev parent reply other threads:[~2018-06-26 10:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2018-06-26 13:13 ` Dave Taht
2018-06-26 8:34 ` Sebastian Moeller
-- strict thread matches above, loose matches on Subject: below --
2018-06-18 17:44 Dave Taht
2018-06-18 17:50 ` Loganaden Velvindron
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
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=87r2ktn7kn.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=pete@heistp.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