From: Michael Tremer Date: Thu, 28 Feb 2019 14:28:07 +0000 (+0000) Subject: suricata: Set max-pending-packets to 1024 X-Git-Tag: v2.23-core131~117^2~28 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=16446608cbe53bcd0873ed48b907b697441d31d1;p=ipfire-2.x.git suricata: Set max-pending-packets to 1024 Signed-off-by: Michael Tremer Signed-off-by: Stefan Schantl --- diff --git a/config/suricata/suricata.yaml b/config/suricata/suricata.yaml index 0ff06f4aeb..b468c9c142 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