Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] lanman2018 cake talk ideas
Date: Fri, 22 Jun 2018 22:35:58 -0700	[thread overview]
Message-ID: <CAA93jw5+TiKRS0yex2eJHkdhK1L4MwCYqs90Vo=umkjWgXPCfw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7vQooBGjCZwkSFk5_Z0i8ZnhkpjJvMCMvanttDGdsHNw@mail.gmail.com>

doing a self review of what I got before I crash

yes, yes, all the slides are out of order. Yes, I should write down
what I intend to say and not have it on the slide

* cake stores one less packet than htb+fq_codel. Anybody got a 2mbit
result for sqm that shows the resulting induced latency?
(2mbit because I'm irked about that 2mbit broadband study in the uk)
* I'll probably substitute my 50x1 ack-filtering result for the 30x1
in the paper (http://blog.cerowrt.org/post/ack_filtering/ ) and burn
no more than a minute on it because I still hate the idea of ack
filtering
* sch_cake (shaped 1gbit ethernet) v sch_fq bql'd at 1Gbit - for A
week NOW! I thought the bandwidth hit from shaping was 1.7 percent.
And I should know better! I realized about an hour ago that it was
(mostly) because we were getting 20% more measurement flows. I pulled
that data out of flent, but perhaps an irtt result shaped to a gbit
would be better (I didn't have irtt on that test). Also that test was
host to host, not through - which I kind of liked. It would probably
irk eric dumazet somewhat to see that result vs sch_fq :)
* I liked mentioning our most remote test site (mauritius), and wanted
to have something that talked about our development process near the
close
* need a final summary slide
* really hate the cake_dst/src/triple isolate graph and wish we had a
better way to express it. pie chart?
* think zooming into 300 flows with a probability of 0 collisions on
the 8 way set associative slide (and yes, the title needs to be
better)
* not sponsored by still motivates me every time it passes by
* liked explaining diffserv's implementation (bandwidth reservation
rather than drop probability)

I figure we have 25 slides tops

  reply	other threads:[~2018-06-23  5:36 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 [this message]
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
  -- 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='CAA93jw5+TiKRS0yex2eJHkdhK1L4MwCYqs90Vo=umkjWgXPCfw@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cake@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