From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 1/2] netfilter: iptables: fix use of cluster match with 32 nodes
Date: Tue, 05 May 2009 17:47:02 +0200 [thread overview]
Message-ID: <4A005F76.7000206@trash.net> (raw)
In-Reply-To: <20090505131403.7241.25297.stgit@Decadence>
Pablo Neira Ayuso wrote:
> This patch fixes a problem when you use 32 nodes in the cluster
> match:
>
> % iptables -I PREROUTING -t mangle -i eth0 -m cluster \
> --cluster-total-nodes 32 --cluster-local-node 32 \
> --cluster-hash-seed 0xdeadbeef -j MARK --set-mark 0xffff
> iptables: Invalid argument. Run `dmesg' for more information.
> % dmesg | tail -1
> xt_cluster: this node mask cannot be higher than the total number of nodes
>
> The problem is related to this checking:
>
> if (info->node_mask >= (1 << info->total_nodes)) {
> printk(KERN_ERR "xt_cluster: this node mask cannot be "
> "higher than the total number of nodes\n");
> return false;
> }
>
> (1 << 32) is 1. Thus, the checking fails.
>
> BTW, I said this before but I insist: I have only tested the cluster
> match with 2 nodes getting ~45% extra performance in an active-active setup.
> The maximum limit of 32 nodes is still completely arbitrary. I'd really
> appreciate if people that have more nodes in their setups let me know.
Applied, thanks Pablo.
next prev parent reply other threads:[~2009-05-05 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 13:13 [PATCH 0/2] netfilter fixes for 2.6.30-rc Pablo Neira Ayuso
2009-05-05 13:14 ` [PATCH 1/2] netfilter: iptables: fix use of cluster match with 32 nodes Pablo Neira Ayuso
2009-05-05 15:47 ` Patrick McHardy [this message]
2009-05-05 13:14 ` [PATCH 2/2] netfilter: ctnetlink: fix wrong message type in user updates Pablo Neira Ayuso
2009-05-05 15:49 ` 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=4A005F76.7000206@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.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 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).