Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: <cake@lists.bufferbloat.net>
Subject: Re: [Cake] BUG_ON vs WARN_ON
Date: Wed, 5 Oct 2016 16:55:54 +0100	[thread overview]
Message-ID: <c86823f5-a4a6-866d-e1de-6be712801057@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAA93jw4qLOc8OQDn3SZRamd8TEkdvJ3=pfsWEGcZV69tvwNPQg@mail.gmail.com>



On 05/10/16 16:53, Dave Taht wrote:
> I did test this version of cake yesterday, had no major problems, aside from:
>
> 1) it seeming not to register drops under some circumstances in the
> statistics. (could be flent)
>
> 2) switching stuff like this
>
> tc qdisc add dev eth0 root cake bandwidth 700mbit
> tc qdisc replace dev eth0 root cake bandwidth 1100mbit # out of cpu,
> basically, at 700 mbit
> tc qdisc replace dev eth0 root cake unlimited # still stuck at 700mbit
>
> kept the thing at 700mbits (out of cpu at that point).
>
> tc qdisc del dev eth0 root cake
> tc qdisc add dev eth0 root cake unlimited # native rate of 1gbit achieved
>

I don't trust tc replace and I'm pretty sure we've been here before.

  reply	other threads:[~2016-10-05 15:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05 15:24 Kevin Darbyshire-Bryant
2016-10-05 15:42 ` Jonathan Morton
2016-10-05 15:45   ` Kevin Darbyshire-Bryant
2016-10-05 15:53     ` Jonathan Morton
2016-10-05 18:53       ` Jonathan Morton
2016-10-07 13:27         ` Kevin Darbyshire-Bryant
2016-10-07 13:35           ` Jonathan Morton
2016-10-07 13:43             ` Kevin Darbyshire-Bryant
2016-10-05 15:53     ` Dave Taht
2016-10-05 15:55       ` Kevin Darbyshire-Bryant [this message]
2016-10-05 15:57         ` Jonathan Morton
2016-10-05 16:38           ` Dave Taht
2016-10-06  3:59             ` Kevin Darbyshire-Bryant
2016-10-06  4:19               ` Dave Taht
2016-10-06  8:12                 ` Jonathan Morton

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=c86823f5-a4a6-866d-e1de-6be712801057@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --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