Thread (8 messages) 8 messages, 4 authors, 2026-03-12

Re: [PATCH net-next] netfilter: conntrack: expose gc_scan_interval_max via sysctl

From: Florian Westphal <fw@strlen.de>
Date: 2026-03-12 12:36:41
Also in: linux-doc, lkml, netfilter-devel

Prasanna S Panchamukhi [off-list ref] wrote:
The conntrack garbage collection worker uses an adaptive algorithm that
adjusts the scan interval based on the average timeout of tracked
entries.  The upper bound of this interval is hardcoded as
GC_SCAN_INTERVAL_MAX (60 seconds).

Expose the upper bound as a new sysctl,
net.netfilter.nf_conntrack_gc_scan_interval_max, so it can be tuned at
runtime without rebuilding the kernel.  The default remains 60 seconds
to preserve existing behavior.  The sysctl is global and read-only in
non-init network namespaces, consistent with nf_conntrack_max and
nf_conntrack_buckets.
This was proposed before, see:

https://lore.kernel.org/netfilter-devel/aO-id5W6Tr7frdHN@strlen.de/ (local)
https://lore.kernel.org/netfilter-devel/aRsuU57juCvsMBKE@strlen.de/ (local)

I did not hear back wrt. the horizon cache.

I'm not 100% opposed to this, but I do wonder if we really can't do
better than the current avg strategy.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help