Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] htb and fq_codel performance optimizations upstream
Date: Sat, 11 Jun 2016 11:40:55 -0700	[thread overview]
Message-ID: <CAA93jw4Q7XjvfFf-N61JGBHkmDHy=ZCARL9UYxXCyqA=deppVA@mail.gmail.com> (raw)

So I pulled net-next today to get:

https://www.mail-archive.com/netdev@vger.kernel.org/msg114172.html

and saw that Eric Dumazet has been going to town on reducing lock
contention for htb and other qdiscs. It is always entertaining to do a
"git log"
and search for his name....

I especially liked the ksoftirqd related patch
3bcb846ca4cf55415d3719e64bb45a124792c589

"    Depending on qdisc setup, I observed a gain of up to 19 % in qdisc
    performance (1016600 pps instead of 853400 pps, using prio+tbf+fq_codel) "


-- 
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org

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

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw4Q7XjvfFf-N61JGBHkmDHy=ZCARL9UYxXCyqA=deppVA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@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