allow for mmap-locked to be configured

This commit is contained in:
m0duspwnens
2024-04-24 13:26:25 -04:00
parent 428fe787c4
commit 0bd0c7b1ec
3 changed files with 7 additions and 0 deletions

View File

@@ -30,6 +30,7 @@ suricata:
cluster-type: cluster_flow
defrag: "yes"
use-mmap: "yes"
mmap-locked: "yes"
threads: 1
tpacket-v3: "yes"
ring-size: 5000

View File

@@ -34,6 +34,7 @@
cluster-type: {{ SURICATAMERGED.config['af-packet']['cluster-type'] }}
defrag: "{{ SURICATAMERGED.config['af-packet'].defrag }}"
use-mmap: "{{ SURICATAMERGED.config['af-packet']['use-mmap'] }}"
mmap-locked: {{ SURICATAMERGED.config['af-packet']['mmap-locked'] }}
threads: {{ SURICATAMERGED.config['af-packet'].threads }}
tpacket-v3: "{{ SURICATAMERGED.config['af-packet']['tpacket-v3'] }}"
ring-size: {{ SURICATAMERGED.config['af-packet']['ring-size'] }}

View File

@@ -83,6 +83,11 @@ suricata:
use-mmap:
advanced: True
readonly: True
mmap-locked:
description: Prevent swapping by locking the memory map.
advanced: True
regex: ^(yes|no)$
helpLink: suricata.html
threads:
description: The amount of worker threads.
helpLink: suricata.html