Pablo Neira Ayuso <pa...@netfilter.org> wrote:
> I would prefer not to expose sysctl knobs, if we don't really know
> what good default values are good, then we cannot expect our users to
> know this for us.
> I would go tune this in a way that this resembles to the previous
I do not see how this is possible without reverting to old per-conntrack
With per-ct timer userspace gets notified the moment the timer
fires, without it notification comes 'when kernel detects the timeout'
which in worst case, as Nicholas describes, is when gc worker comes
You can run the gc worker every jiffie of course, but thats just
wasting cpu cycles (and you still get a small delay).
I don't see a way to do run-time tuning except faster restarts when
old entries start accumulating. This is what the code tries to do,
perhaps you have a better idea for the 'next gc run' computation.