Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Pete Heist <peteheist@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: "Dave Täht" <dave.taht@gmail.com>,
	"Cake List" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] small cake_hash optimization?
Date: Thu, 23 Nov 2017 10:30:58 +0100	[thread overview]
Message-ID: <65345DE4-8E75-4913-9FFF-2823BF70AB85@gmail.com> (raw)
In-Reply-To: <BA486EAF-4DD2-4E6F-9927-61A36E2AF7FD@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 1653 bytes --]


> On Nov 23, 2017, at 9:00 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
> 
> Hi Pete,
> 
> 	I should have mentioned "overhead 64 mpu 84" only make sense in combination with a shaper limit (well, they will make sure the cake statistics will be more reflective of what is happening on the ethernet wire, but I am not sure whether that is worth the run-time cost the overhead calculation incurs).
> 
> Somewhat unrelated, I wondered about all the excitement about irtt and cloned the repository to my mac, and was absolutely delighted to realize that irtt will also effortlessly work under macos. I only have run the demo from the readme.md with both client and server running at the same machine, but I got results that look reasonable on first sight (but I admit I really do not know exact;y what to expect). This is really great!

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.

Glad to hear irtt runs for you! I was waiting to post something until I clean up some more things in the todo list, but since you found it, let me know (file an Issue) if you find any problems. Also, if you have something later than El Capitan, I might be interested to see the output from “irtt sleep” or ten seconds or so from “irtt clock”, as I’m gradually learning about timer/clock behavior on different OSs. I guess it could also be filed as an Issue, so we don’t add too much to the cake list...

[-- Attachment #2: Type: text/html, Size: 5109 bytes --]

  reply	other threads:[~2017-11-23  9:31 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 [this message]
2017-11-23  9:36           ` Pete Heist
2017-11-23 16:21             ` Dave Taht
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=65345DE4-8E75-4913-9FFF-2823BF70AB85@gmail.com \
    --to=peteheist@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=moeller0@gmx.de \
    /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