From: Florian Westphal <fw@strlen.de>
To: Prasanna Panchamukhi <panchamukhi@arista.com>
Cc: netfilter-devel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Phil Sutter <phil@nwl.cc>,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, coreteam@netfilter.org
Subject: Re: [PATCH net-next] netfilter: conntrack: expose gc_scan_interval_max via sysctl
Date: Fri, 13 Mar 2026 00:10:23 +0100 [thread overview]
Message-ID: <abNH3xxxAU7U4zz5@strlen.de> (raw)
In-Reply-To: <CACqWiXD2_O32K4NhmNBZrAUG7U9-N93LTFjJHG6Tq=4vuafNuA@mail.gmail.com>
Prasanna Panchamukhi <panchamukhi@arista.com> wrote:
> Our primary goal is to cap the maximum time taken by the GC to clean
> up expired entries. We rely on user-space notifications to clean up
> these entries from the hardware, so ensuring a predictable upper bound
> is important for our use case.
Sure, but why can't we try to give a better default behavior?
while true; conntrack -L >/dev/null;done
basically does what you want already (but in a dumb way).
> Regarding the adaptive strategy, we are using this sysctl to address
> environments where the current average-based calculation delays the
> cleanup of short-lived entries.
Yes, and I did propose to adapt the existing strategy to provide more
timely notifications.
prev parent reply other threads:[~2026-03-12 23:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 19:40 [PATCH net-next] netfilter: conntrack: expose gc_scan_interval_max via sysctl Prasanna S Panchamukhi
2026-03-12 12:12 ` Fernando Fernandez Mancera
2026-03-12 12:15 ` Fernando Fernandez Mancera
2026-03-12 21:44 ` Prasanna Panchamukhi
2026-03-12 12:36 ` Florian Westphal
2026-03-12 22:31 ` Prasanna Panchamukhi
2026-03-12 22:42 ` Pablo Neira Ayuso
2026-03-12 23:10 ` Florian Westphal [this message]
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=abNH3xxxAU7U4zz5@strlen.de \
--to=fw@strlen.de \
--cc=corbet@lwn.net \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=panchamukhi@arista.com \
--cc=phil@nwl.cc \
--cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.