From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. b3ee263b07d24c115614e2d5ceb909f1afe10c80
Date: Thu, 06 Apr 2017 19:13:53 +0100 [thread overview]
Message-ID: <20170406181353.DF05D10853C3@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1668 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via b3ee263b07d24c115614e2d5ceb909f1afe10c80 (commit)
from d0755f4cb2e8d1d1332f6624b6d8d7adf0db9192 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit b3ee263b07d24c115614e2d5ceb909f1afe10c80
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Apr 6 19:12:06 2017 +0100
QoS: Enable IMQ multi queueing
This increases throughput when QoS is activated
since now all available CPU cores will be used
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/qos/makeqosscripts.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/qos/makeqosscripts.pl b/config/qos/makeqosscripts.pl
index b623cbe..1980961 100644
--- a/config/qos/makeqosscripts.pl
+++ b/config/qos/makeqosscripts.pl
@@ -411,7 +411,7 @@ print <<END
insmod ipt_IMQ
sleep 2
fi
- modprobe imq numdevs=1
+ modprobe imq numdevs=1 numqueues=\$(grep -c "^processor" /proc/cpuinfo || echo 1)
ip link set $qossettings{'IMQ_DEV'} up
### ADD HTB QDISC FOR $qossettings{'IMQ_DEV'}
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2017-04-06 18:13 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170406181353.DF05D10853C3@git01.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.org \
/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