Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Pete Heist <peteheist@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] small cake_hash optimization?
Date: Wed, 22 Nov 2017 19:43:52 +0100	[thread overview]
Message-ID: <E3880313-03A9-4C9B-B170-9DA9F1FE8E52@gmail.com> (raw)
In-Reply-To: <CAA93jw7pJESFowu28tC3yruQca1OTU=0GO4z-oSTvyBeksFwKg@mail.gmail.com>


> On Nov 22, 2017, at 7:33 PM, Dave Taht <dave.taht@gmail.com> wrote:
> 
> On Wed, Nov 22, 2017 at 4:37 AM, Pete Heist <peteheist@gmail.com> wrote:
>> 
>> Ok, at least a little crude testing with sar:
>> 
>> https://docs.google.com/spreadsheets/d/1LKoq5NaswuHm9H1atXoZA1AhNDg6L4UYS3Pn5lCsb1I/edit#gid=0
>> 
>> ~10% less cake CPU at GigE in this case?
> 
> Divides do hurt, particularly if you can't do them out of order. But
> that seems like a lot.

Hrm, I tried a second test to make sure fairness still works (it does) but this time got a slight _negative_ result (rrul_be fair tab). So this calls into question whether or not my testing method is very good, and also whether or not the change actually helps much.

This time I used "cake unlimited besteffort dual-srchost overhead 64 mpu 84” (overheads from Sebastian, just rely on bql).

I might try again with 950mbit limiting, and ‘perf’ instead.

Also I noted that the ‘lan’ keyword seemed to adversely affect host fairness, so I stopped using it. I’ll address that separately when there’s time.

>> What’s a better tool for timing
>> kernel module functions?
> 
> Use "perf"
> 
> https://en.wikipedia.org/wiki/Perf_(Linux)

Ok, will see if I can give it a try.

  reply	other threads:[~2017-11-22 18:43 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 [this message]
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
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=E3880313-03A9-4C9B-B170-9DA9F1FE8E52@gmail.com \
    --to=peteheist@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@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