From: Dave Taht <dave.taht@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] single softirq handler for shaping?
Date: Sun, 12 Apr 2015 15:11:51 -0700 [thread overview]
Message-ID: <CAA93jw4fEzX3L4pSNvK=WNwgwi08fsEvA8DS4igqpgRcgFeNbQ@mail.gmail.com> (raw)
All the new routers are multicore - the mt72 is 4 cores, I think the
linksys 1900ac is dual core.
And it is not clear to me if we are single threaded on the softirq
handler or other parts of the shaping side of all this. ? I seem to only
see one softirq handler running on the edgerouter pro with htb + fq_codel,
for example.
We usually run two instances of the shaper - one on inbound - the
hard task, and the other on outbound (usually much less hard on cpu)
So one thread per shaper (if sufficient cpus are available) queue
might scale better, if we are presently only using one.
--
Dave Täht
Open Networking needs **Open Source Hardware**
https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67
reply other threads:[~2015-04-12 22:11 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/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='CAA93jw4fEzX3L4pSNvK=WNwgwi08fsEvA8DS4igqpgRcgFeNbQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--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