Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Pete Heist <peteheist@gmail.com>
Cc: Sebastian Moeller <moeller0@gmx.de>,
	Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] small cake_hash optimization?
Date: Thu, 23 Nov 2017 08:21:08 -0800	[thread overview]
Message-ID: <CAA93jw5cFqoGbuBuWpf90tCJxSMjwXX=uin6J8omRgd3Zt37Yg@mail.gmail.com> (raw)
In-Reply-To: <B8C4A643-59A1-408C-949E-C2F87187AF2A@gmail.com>

On Thu, Nov 23, 2017 at 1:36 AM, Pete Heist <peteheist@gmail.com> wrote:
>
>> On Nov 23, 2017, at 10:30 AM, Pete Heist <peteheist@gmail.com> wrote:
>>
>> Thanks for the overhead info. I used that in my latest tests. That makes me wonder if those overheads could be defaulted when Cake knows Ethernet is being used with rate limiting? I know a goal is to make cake easier to configure so such things are examples of what people are likely to miss.
>
> BTW I realize there’s no way cake can know what the overheads should actually be, just to make sure the defaults are sensible I guess. I know overheads are not an easy thing.

I note that the man page needs love.

> _______________________________________________
> 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:[~2017-11-23 16:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22 10:06 Pete Heist
2017-11-22 12:37 ` Pete Heist
2017-11-22 13:51   ` Sebastian Moeller
2017-11-22 18:33   ` Dave Taht
2017-11-22 18:43     ` Pete Heist
2017-11-23  8:00       ` Sebastian Moeller
2017-11-23  9:30         ` Pete Heist
2017-11-23  9:36           ` Pete Heist
2017-11-23 16:21             ` Dave Taht [this message]
2017-11-23 16:48               ` Sebastian Moeller
2017-11-23 16:57                 ` Dave Taht
2017-11-23 10:22           ` Sebastian Moeller
2017-11-22 18:38   ` Dave Taht
2017-11-22 18:49     ` Pete Heist
2017-11-22 21:19       ` Pete Heist
2017-11-22 21:26         ` Dave Taht

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='CAA93jw5cFqoGbuBuWpf90tCJxSMjwXX=uin6J8omRgd3Zt37Yg@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    --cc=peteheist@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