From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Harald Welte <laforge@netfilter.org>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH 0/10] updates for ctnetlink and conntrack core
Date: Fri, 07 Jul 2006 08:20:15 +0200 [thread overview]
Message-ID: <44ADFD1F.7050602@trash.net> (raw)
In-Reply-To: <44ADF800.80701@trash.net>
Patrick McHardy wrote:
> In some very unscientific tests it showed a difference of about
> 4% when dumping everything compared to only diffs (measured
> with conntrack accounting enabled). Not something to easily
> throw away, but I bet we can easily increase the netlink bandwidth
> for ctnetlink by using more reasonable allocation size and
> avoiding the netlink_trim call for every single packet.
Some more unscientific tests: saving the netlink_trim call by using
an allocation size of 200 reduces overhead for the entire notification
function (including broadcasting) by about 13% (and also reduces
the overruns experienced by conntrack -E for ~390000 packets with
65536 new connections from 17 to 7, which I don't really understand
since it shouldn't save any netlink bandwidth and this is a SMP system).
next prev parent reply other threads:[~2006-07-07 6:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 2:11 [PATCH 0/10] updates for ctnetlink and conntrack core Pablo Neira Ayuso
2006-07-07 5:13 ` Patrick McHardy
2006-07-07 5:58 ` Patrick McHardy
2006-07-07 6:20 ` Patrick McHardy [this message]
2006-07-07 13:46 ` Pablo Neira Ayuso
2006-07-10 4:42 ` Patrick McHardy
2006-07-13 20:01 ` Pablo Neira Ayuso
2006-07-19 16:39 ` Patrick McHardy
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=44ADFD1F.7050602@trash.net \
--to=kaber@trash.net \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pablo@netfilter.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.