From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Holger Eitzenberger <holger@eitzenberger.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] NFQUEUE: add --queue-cpu-fanout parameter
Date: Tue, 2 Apr 2013 01:29:47 +0200 [thread overview]
Message-ID: <20130401232947.GA12381@localhost> (raw)
In-Reply-To: <20130323200608.668651644@eitzenberger.org>
Hi Holger,
On Sat, Mar 23, 2013 at 09:04:05PM +0100, Holger Eitzenberger wrote:
> Signed-off-by: Holger Eitzenberger <holger@eitzenberger.org>
> Index: iptables/extensions/libxt_NFQUEUE.c
> ===================================================================
> --- iptables.orig/extensions/libxt_NFQUEUE.c 2013-03-23 19:43:11.000000000 +0100
> +++ iptables/extensions/libxt_NFQUEUE.c 2013-03-23 19:43:29.000000000 +0100
> @@ -13,8 +13,10 @@
> O_QUEUE_NUM = 0,
> O_QUEUE_BALANCE,
> O_QUEUE_BYPASS,
> + O_QUEUE_CPU_FANOUT,
> F_QUEUE_NUM = 1 << O_QUEUE_NUM,
> F_QUEUE_BALANCE = 1 << O_QUEUE_BALANCE,
> + F_QUEUE_CPU_FANOUT = 1 << O_QUEUE_CPU_FANOUT,
> };
>
> static void NFQUEUE_help(void)
> @@ -37,7 +39,15 @@
> {
> NFQUEUE_help_v1();
> printf(
> -" --queue-bypass Bypass Queueing if no queue instance exists.\n");
> +" --queue-bypass Bypass Queueing if no queue instance exists.\n"
> +" --queue-cpu-fanout Use current CPU (no hashing)\n");
> +}
> +
> +static void NFQUEUE_help_v3(void)
> +{
> + NFQUEUE_help_v2();
> + printf(
> +" --queue-cpu-fanout Use current CPU (no hashing)\n");
> }
>
> #define s struct xt_NFQ_info
> @@ -48,6 +58,8 @@
> {.name = "queue-balance", .id = O_QUEUE_BALANCE,
> .type = XTTYPE_UINT16RC, .excl = F_QUEUE_NUM},
> {.name = "queue-bypass", .id = O_QUEUE_BYPASS, .type = XTTYPE_NONE},
> + {.name = "queue-cpu-fanout", .id = O_QUEUE_CPU_FANOUT,
> + .type = XTTYPE_NONE, .also = O_QUEUE_BALANCE},
I think we have to add O_QUEUE_CPU_FANOUT here to make sure both
queue-balance and queue-cpu-fanout are not used both incorrectly
together. That also needs some code a new .x6_fcheck function to
validate this.
Could you also send me the corresponding manpage update for this?
Thanks!
next prev parent reply other threads:[~2013-04-01 23:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 20:04 [PATCH v2 0/3] NFQUEUE: introduce CPU fanout Holger Eitzenberger
2013-03-23 20:04 ` [PATCH v2 1/3] " Holger Eitzenberger
2013-04-01 23:26 ` Pablo Neira Ayuso
2013-03-23 20:04 ` [PATCH v2 2/3] NFQUEUE: coalesce IPv4 and IPv6 hashing Holger Eitzenberger
2013-04-01 23:26 ` Pablo Neira Ayuso
2013-03-23 20:04 ` [PATCH v2 3/3] NFQUEUE: add --queue-cpu-fanout parameter Holger Eitzenberger
2013-04-01 23:29 ` Pablo Neira Ayuso [this message]
2013-04-02 10:35 ` Holger Eitzenberger
2013-04-02 11:26 ` Pablo Neira Ayuso
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=20130401232947.GA12381@localhost \
--to=pablo@netfilter.org \
--cc=holger@eitzenberger.org \
--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).