From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. f903d3a6f0c4a3f2e5251fda7ea2d1b788606294
Date: Fri, 05 Apr 2019 18:20:24 +0100 [thread overview]
Message-ID: <20190405172025.43D4A84FDB0@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1615 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 f903d3a6f0c4a3f2e5251fda7ea2d1b788606294 (commit)
from aa20f1b27727e8ed3d3d164eb3a66faa4ea0d4a4 (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 f903d3a6f0c4a3f2e5251fda7ea2d1b788606294
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Apr 4 22:01:54 2019 +0100
suricata: Disable CPU affinity
Benchmarks have shown, that this is making the IPS slower
across various hardware
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/suricata/suricata.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/suricata/suricata.yaml b/config/suricata/suricata.yaml
index 8580827a1..f37294d54 100644
--- a/config/suricata/suricata.yaml
+++ b/config/suricata/suricata.yaml
@@ -697,7 +697,7 @@ spm-algo: auto
# Suricata is multi-threaded. Here the threading can be influenced.
threading:
- set-cpu-affinity: yes
+ set-cpu-affinity: no
# Tune cpu affinity of threads. Each family of threads can be bound
# on specific CPUs.
#
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-04-05 17:20 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=20190405172025.43D4A84FDB0@people01.i.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