netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Schaaf <netdev@bof.de>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH v2 -next 1/2] netfilter: iptables: separate counters from iptables rules
Date: Fri, 29 May 2015 13:32:22 +0200	[thread overview]
Message-ID: <2679129.rhlPpvF55Y@rofl> (raw)
In-Reply-To: <1432846296-26396-1-git-send-email-fw@strlen.de>

Hi Florian (+ list), (resend without HTML part...)

would it be feasible to have sysctl knobs to disable the counters? 

Easiest approach might be to keep all the counter memory allocation 
as it is (or as it is changed with your current work), and just not count at 
packet processing time. Which should make things a bit faster (no 
cache pollution for the RMW counter access of any matching rules.) 

More complicated approach might even save the whole counter 
memory consumption, faking 0 values when returning counters to 
userlevel, and ignoring userlevel supplied values (iptables-restore) 

best regards
  Patrick



  parent reply	other threads:[~2015-05-29 11:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28 20:51 [PATCH v2 -next 1/2] netfilter: iptables: separate counters from iptables rules Florian Westphal
2015-05-28 20:51 ` [PATCH v2 -next 2/2] netfilter: store rules per NUMA node instead of per cpu Florian Westphal
2015-05-28 21:38   ` Eric Dumazet
2015-05-28 21:52     ` Florian Westphal
2015-05-28 22:04       ` Eric Dumazet
2015-05-29  9:41         ` Florian Westphal
2015-05-28 21:33 ` [PATCH v2 -next 1/2] netfilter: iptables: separate counters from iptables rules Eric Dumazet
2015-05-28 21:45   ` Florian Westphal
2015-05-28 21:54     ` Eric Dumazet
2015-05-29 10:05       ` Florian Westphal
2015-05-29 10:32         ` Eric Dumazet
2015-05-29 11:32 ` Patrick Schaaf [this message]
2015-06-05 12:28   ` Florian Westphal

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=2679129.rhlPpvF55Y@rofl \
    --to=netdev@bof.de \
    --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).