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:14:10 -0700	[thread overview]
Message-ID: <CAA93jw7vQooBGjCZwkSFk5_Z0i8ZnhkpjJvMCMvanttDGdsHNw@mail.gmail.com> (raw)
In-Reply-To: <BAC26A5A-8CDA-4DEE-905E-97419263645D@heistp.net>

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.

off to pack
On Fri, Jun 22, 2018 at 1:05 AM Pete Heist <pete@heistp.net> wrote:
>
>
> On Jun 22, 2018, at 9:45 AM, Felix Resch <fuller@beif.de> wrote:
>
> ... has no Wikipedia page yet ...
>
>
> here you go https://en.wikipedia.org/wiki/Draft:Megabit_myth
>
>
> Thanks! Now the problem is solved. :)
>
> I only had some second thoughts, and let’s get this right and be consistent, is it:
>
> 1) Megabit myth
> 2) Megabits myth
> 3) Megabits per second myth
>
> #3 is the accurate one, but in this day and age every syllable can somehow slow an idea down. I’m leaning towards #2. I’ve also heard non-technical people say “how many Megabits is it?” when referring to an Internet connection, as if the “per second” part is already too much to handle. :)
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake



-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

  reply	other threads:[~2018-06-23  5:14 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 [this message]
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
  -- 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=CAA93jw7vQooBGjCZwkSFk5_Z0i8ZnhkpjJvMCMvanttDGdsHNw@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