From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next] netfilter: conntrack: remove packet hotpath stats
Date: Mon, 12 Sep 2016 20:09:34 +0200 [thread overview]
Message-ID: <20160912180934.GA2471@salvia> (raw)
In-Reply-To: <1473627353-27981-1-git-send-email-fw@strlen.de>
On Sun, Sep 11, 2016 at 10:55:53PM +0200, Florian Westphal wrote:
> These counters sit in hot path and do show up in perf, this is especially
> true for 'found' and 'searched' which get incremented for every packet
> processed.
>
> Information like
>
> searched=212030105
> new=623431
> found=333613
> delete=623327
>
> does not seem too helpful nowadays:
>
> - on busy systems found and searched will overflow every few hours
> (these are 32bit integers), other more busy ones every few days.
>
> - for debugging there are better methods, such as iptables' trace target,
> the conntrack log sysctls. Nowadays we also have perf tool.
>
> This removes packet path stat counters except those that
> are expected to be 0 (or close to 0) on a normal system, e.g.
> 'insert_failed' (race happened) or 'invalid' (proto tracker rejects).
>
> The insert stat is retained for the ctnetlink case.
> The found stat is retained for the tuple-is-taken check when NAT has to
> determine if it needs to pick a different source address.
Applied, thanks.
prev parent reply other threads:[~2016-09-12 18:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 20:55 [PATCH nf-next] netfilter: conntrack: remove packet hotpath stats Florian Westphal
2016-09-12 18:09 ` Pablo Neira Ayuso [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=20160912180934.GA2471@salvia \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).