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] Possible BUG - parent backlog incorrectly updated in case of NET_XMIT_CN
Date: Sat, 11 Jun 2016 10:11:44 +0100	[thread overview]
Message-ID: <575BD5D0.4060702@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <5756E2CA.2020700@darbyshire-bryant.me.uk>



On 07/06/16 16:05, Kevin Darbyshire-Bryant wrote:
>
>
> On 07/06/16 15:50, Jonathan Morton wrote:
>>> On 7 Jun, 2016, at 14:20, Kevin Darbyshire-Bryant 
>>> <kevin@darbyshire-bryant.me.uk> wrote:
>>>
>>> I had a nose at CAKE but couldn't quit work out if a similar issue 
>>> is present but I suspect it is. Certainly if Eric can't get it right 
>>> "My prior attempt to fix the backlogs of parents failed." then it's 
>>> not an 'obvious to solve' problem :-)
>> It appears my code already handles it correctly.  This is most likely 
>> because it inherited the analogous handling from the old function 
>> called here.
>
> I was intrigued by how in the case of XMIT_CN he reports the backlog 
> without the packet just dropped 'cos the parent qdisc won't include 
> that length in its calculations because we reported we dropped the 
> packet.  Preventing double accounting.
>
> +    /* As we dropped packet(s), better let upper stack know this.
> +     * If we dropped a packet for this flow, return NET_XMIT_CN,
> +     * but in this case, our parents wont increase their backlogs.
> +     */
> +    prev_qlen -= sch->q.qlen;
> +    prev_backlog -= sch->qstats.backlog;
> +    if (ret == idx) {
> +        qdisc_tree_reduce_backlog(sch, prev_qlen - 1,
> +                      prev_backlog - qdisc_pkt_len(skb)); <<<<here
> +        return NET_XMIT_CN;
> +    }
> +    qdisc_tree_reduce_backlog(sch, prev_qlen, prev_backlog);
> +    return NET_XMIT_SUCCESS;

And now there's a version 2 of Eric's fix: 
http://marc.info/?l=linux-netdev&m=146507012302643&w=2

Does this change apply to cake?

Cheers,

Kevin



  reply	other threads:[~2016-06-11  9:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07 11:20 Kevin Darbyshire-Bryant
2016-06-07 14:50 ` Jonathan Morton
2016-06-07 15:05   ` Kevin Darbyshire-Bryant
2016-06-11  9:11     ` Kevin Darbyshire-Bryant [this message]
2016-06-11 16:41       ` Jonathan Morton
2016-06-12 16:31         ` Eric Dumazet
2016-06-12 16:40           ` Dave Taht
2016-06-12 17:48             ` Eric Dumazet
2016-06-12 17:51               ` Jonathan Morton
2016-06-12 18:19                 ` Eric Dumazet
2016-06-12 17:59           ` Jonathan Morton
2016-06-12 19:04             ` Eric Dumazet
2016-06-12 20:40               ` Benjamin Cronce

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=575BD5D0.4060702@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