Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Jonathan Morton <chromatix99@gmail.com>, cake@lists.bufferbloat.net
Subject: Re: [Cake] Possible BUG - parent backlog incorrectly updated in case of NET_XMIT_CN
Date: Sun, 12 Jun 2016 09:40:45 -0700	[thread overview]
Message-ID: <CAA93jw5v-RCPSngT4wmXjjS4MwT61EntcjaYiaV0hmfyDsPAFw@mail.gmail.com> (raw)
In-Reply-To: <1465749085.7945.81.camel@edumazet-glaptop3.roam.corp.google.com>

Eric:

Quick side question (from trying to understand the qdisc locking fixes
you recently landed in net-next)

In the sqm-scripts, we are usually in a position where we are doing
both inbound and outbound rate limiting (htb + fq_codel or cake). We
typically run out of cpu or have mis-behavior on the inbound side, and
the cpu bottleneck appears to be in ksoftirqd.

A) In my failing to make sense of all the dialog around these patches
( https://lwn.net/Articles/687617/  ), it sounds like this (inbound
and outbound) processing are still locked to a single thread,
essentially?

B) But you have eliminated lot of overhead in basic qdisc processing
to much cpu benefit and we should consider backporting these changes
to lede/openwrt (4.4)?

  reply	other threads:[~2016-06-12 16:40 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
2016-06-11 16:41       ` Jonathan Morton
2016-06-12 16:31         ` Eric Dumazet
2016-06-12 16:40           ` Dave Taht [this message]
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=CAA93jw5v-RCPSngT4wmXjjS4MwT61EntcjaYiaV0hmfyDsPAFw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=eric.dumazet@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