From: Patrick McHardy <kaber@trash.net>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: netdev@vger.kernel.org, netfilter@vger.kernel.org,
Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>
Subject: Re: conntrack timers usage
Date: Mon, 13 Oct 2008 15:20:39 +0200 [thread overview]
Message-ID: <48F34B27.50001@trash.net> (raw)
In-Reply-To: <200810130149.25635.denys@visp.net.lb>
Denys Fedoryshchenko wrote:
> The story with excessive timers usage continue.
>
> Here is my results from /proc/timer_stats for 30 seconds (150Mbps traffic)
> ...
> And here is netfilter usage, looks like ....
> I did also sysctl -w net.netfilter.nf_conntrack_acct=0
>
> 1, 0 swapper __nf_ct_refresh_acct (death_by_timeout)
> 1, 0 swapper __nf_ct_refresh_acct (death_by_timeout)
> 1, 0 swapper __nf_ct_refresh_acct (death_by_timeout)
> 1, 0 swapper __nf_ct_refresh_acct (death_by_timeout)
> 1, 0 swapper __nf_ct_refresh_acct (death_by_timeout)
> 1, 0 swapper __nf_conntrack_confirm (death_by_timeout)
> 1, 0 swapper __nf_conntrack_confirm (death_by_timeout)
> 1, 0 swapper __nf_conntrack_confirm (death_by_timeout)
> 1, 0 swapper __nf_conntrack_confirm (death_by_timeout)
> 1, 0 swapper __nf_conntrack_confirm (death_by_timeout)
> 1, 0 swapper __nf_conntrack_confirm (death_by_timeout)
> 1, 0 swapper __nf_conntrack_confirm (death_by_timeout)
> 1, 0 swapper __nf_conntrack_confirm (death_by_timeout)
> ....
>
> Router-Dora ~ # cat /proc/timer_stats |grep '__nf'|wc -l
> 1005
>
> Is it important to do so much calls to timers in conntrack?
> Precision on it is not more than 1 second.
There's one timer per conntrack. As you noticed, we only update
timers for delta >= 1s, but with many conntracks, that still adds
up to a lot.
prev parent reply other threads:[~2008-10-13 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 22:49 conntrack timers usage Denys Fedoryshchenko
2008-10-13 13:20 ` Patrick McHardy [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=48F34B27.50001@trash.net \
--to=kaber@trash.net \
--cc=denys@visp.net.lb \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@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).