Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Long-RTT broken again
Date: Tue, 3 Nov 2015 09:34:29 +0100	[thread overview]
Message-ID: <F1B6B3E1-F4B4-4C26-B31F-3B542BC8157E@gmx.de> (raw)
In-Reply-To: <BADD5BC8-78DF-4F67-81DF-785D33318676@gmail.com>

Hi Jonathan,

On Nov 3, 2015, at 09:25 , Jonathan Morton <chromatix99@gmail.com> wrote:

> 
>> On 3 Nov, 2015, at 10:20, Sebastian Moeller <moeller0@gmx.de> wrote:
>> 
>> Also what about the BUG_ON I managed to trigger during my testing?
> 
> That turned out to be a flawed condition, which I’ve already fixed.

	Excellent, thanks a lot. I would not have repeatedly brought this up, if I had known it fixed, Call me weird, but I am not too keen to look at the source to see whether “reported” issues are fixed. I also note it still is a BUG_ON ()actually there are two in sch_cake) and that still has the issue whether cake is important enough to hose a computer on failure… My understanding from luring on LKML is that under-justified BUG_ONs are frowned upon… Why is that an issue? In my case I needed physical access to reboot the machine, which for remote servers gets difficult...

>  It’s necessary for something like that to be there, because there is a fixed, static allocation of tins; exceeding that number would result in a buffer overflow.  The only way to do so is to add a new Diffserv scheme with more than eight tins, which isn’t outside the bounds of possibility in the future, though unlikely in the short term.

	Sure, but BUG_ON is the big gun that will most likely make the machine unusable (at least it wedged my opensuse 13.2 machine hard enough that a reboot was required); which I believe is too drastic for a failed qdisc, but I could be wrong…

Best Regards
	Sebastian

> 
> - Jonathan Morton
> 


  reply	other threads:[~2015-11-03  8:34 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-02 16:53 Toke Høiland-Jørgensen
2015-11-02 18:29 ` Sebastian Moeller
2015-11-03  1:39   ` Jonathan Morton
2015-11-03  8:20     ` Sebastian Moeller
2015-11-03  8:25       ` Jonathan Morton
2015-11-03  8:34         ` Sebastian Moeller [this message]
2015-11-03 10:29           ` Kevin Darbyshire-Bryant
2015-11-03 11:08             ` Sebastian Moeller
2015-11-03 11:45               ` Toke Høiland-Jørgensen
2015-11-03 11:57       ` Toke Høiland-Jørgensen
2015-11-03 12:41         ` Sebastian Moeller
2015-11-03 11:50     ` Toke Høiland-Jørgensen
2015-11-03 16:43       ` Jonathan Morton
2015-11-03 17:05         ` Toke Høiland-Jørgensen
2015-11-03 17:11           ` Sebastian Moeller
2015-11-03 17:25             ` Toke Høiland-Jørgensen
2015-11-03 17:31               ` Jonathan Morton
2015-11-03 17:33                 ` Toke Høiland-Jørgensen
2015-11-03 17:46                   ` Sebastian Moeller
2015-11-03 17:49                     ` Toke Høiland-Jørgensen
2015-11-03 17:52                       ` Sebastian Moeller
2015-11-03 17:54                         ` Toke Høiland-Jørgensen
2015-11-03 17:57                           ` Sebastian Moeller
2015-11-03 17:59                             ` Toke Høiland-Jørgensen
2015-11-03 18:06                               ` Sebastian Moeller
2015-11-03 19:17                                 ` Jonathan Morton
2015-11-03 19:24                                   ` Sebastian Moeller
2015-11-05 14:36         ` Toke Høiland-Jørgensen
2015-11-05 19:30           ` Jonathan Morton
2015-11-06 11:00             ` Toke Høiland-Jørgensen
2015-11-06 14:15               ` Toke Høiland-Jørgensen
2015-11-06 15:09                 ` Toke Høiland-Jørgensen
2015-11-07  5:02                 ` Jonathan Morton
2015-11-07  5:16                   ` Dave Taht
2015-11-07  6:49                     ` Jonathan Morton
2015-11-07  8:48                   ` Toke Høiland-Jørgensen
2015-11-07 10:51                     ` Jonathan Morton
2015-11-07 13:06                       ` Jonathan Morton
2015-11-07 13:42                         ` Toke Høiland-Jørgensen
2015-11-07 16:34                         ` Toke Høiland-Jørgensen
2015-11-07 13:44                       ` Toke Høiland-Jørgensen
2015-11-07 15:08                       ` Sebastian Moeller
2015-11-07 16:24                         ` Toke Høiland-Jørgensen
2015-11-07 18:25                           ` Sebastian Moeller
2015-11-07 19:32                           ` Kevin Darbyshire-Bryant
2015-11-08 16:29                             ` Dave Taht
2015-11-11 10:23                               ` Kevin Darbyshire-Bryant

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=F1B6B3E1-F4B4-4C26-B31F-3B542BC8157E@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@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