From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dave Taht <dave.taht@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 10:48:53 -0700 [thread overview]
Message-ID: <1465753733.7945.85.camel@edumazet-glaptop3.roam.corp.google.com> (raw)
In-Reply-To: <CAA93jw5v-RCPSngT4wmXjjS4MwT61EntcjaYiaV0hmfyDsPAFw@mail.gmail.com>
On Sun, 2016-06-12 at 09:40 -0700, Dave Taht wrote:
> 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?
Om a router, these discussions should not matter really, since the
workload is about receiving/sending packets without user space
intervention (well... I do hope this !)
>
> 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)?
It is possible that my recent patches avoiding the throttled bit
manipulation might help. I measured between 7% and 8% change in my tests
on x86 with HTB qdisc.
e69f73bfecb0178ae6bd20eb778211739cd71fab Merge branch 'remove-qdisc-throttle'
45f50bed1d808794e514e9eed0e579a8756ce2ba net_sched: remove generic throttled management
42117927cab5a13192ecc227bea19da5059ffc6c net_sched: netem: remove qdisc_is_throttled() use
cca605dd4b3b2bfa381250b7dbbe16b124916f24 net_sched: cbq: remove a flaky use of qdisc_is_throttled()
8fe6a79fb8088a759b3dc57eb641fc3183ad72b8 net_sched: sch_plug: use a private throttled status
next prev parent reply other threads:[~2016-06-12 17:48 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
2016-06-12 17:48 ` Eric Dumazet [this message]
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=1465753733.7945.85.camel@edumazet-glaptop3.roam.corp.google.com \
--to=eric.dumazet@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--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