Re: [PATCH v3] nf_conntrack: sysctl: expose gc worker scan interval via sysctl

From: Florian Westphal
Date: Mon Nov 17 2025 - 09:32:32 EST


Vimal Agrawal <avimalin@xxxxxxxxx> wrote:
> How about we keep only the minimum expiry time out of all (one which
> is going to expire next) and if there are listeners then we just
> schedule gc_worker to that minimum time (and do this only if there are
> ctnetlink listeners in userspace)? so that we don't delay even if
> there is 1 such low value timer expiring in the near future.
> Do you think it will cause too frequent wake ups for gc_worker?

Yes, I am worried about 1k extra wakeups/s in worst case
(we always have exactly one flow which has 1 jiffy remaining).

Plus we might have per-net workers in the future, so it could get
worse.