[02/20] suricata: Set max-pending-packets to 1024

Message ID 20190228142825.5153-3-michael.tremer@ipfire.org
State Accepted
Commit 16446608cbe53bcd0873ed48b907b697441d31d1
Series Suricata Configuration Updates |

Commit Message

Michael Tremer 1 Mar 2019, 1:28 a.m. UTC
  Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
 config/suricata/suricata.yaml | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)


diff --git a/config/suricata/suricata.yaml b/config/suricata/suricata.yaml
index 301a157a3..d94de87f1 100644
--- a/config/suricata/suricata.yaml
+++ b/config/suricata/suricata.yaml
@@ -412,11 +412,7 @@  host-mode: auto
 # Number of packets preallocated per thread. The default is 1024. A higher number 
 # will make sure each CPU will be more easily kept busy, but may negatively 
 # impact caching.
-# If you are using the CUDA pattern matcher (mpm-algo: ac-cuda), different rules
-# apply. In that case try something like 60000 or more. This is because the CUDA
-# pattern matcher buffers and scans as many packets as possible in parallel.
-#max-pending-packets: 1024
+max-pending-packets: 1024
 # Runmode the engine should use. Please check --list-runmodes to get the available
 # runmodes for each packet acquisition method. Defaults to "autofp" (auto flow pinned