From: Eric Dumazet <eric.dumazet@gmail.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Jan Engelhardt <jengelh@medozas.de>,
Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
Patrick McHardy <kaber@trash.net>
Subject: Re: [PATCH v4] netfilter: ipt_CLUSTERIP: remove "no conntrack!"
Date: Thu, 13 Jan 2011 17:48:49 +0100 [thread overview]
Message-ID: <1294937329.3570.304.camel@edumazet-laptop> (raw)
In-Reply-To: <4D2F29D6.3040600@netfilter.org>
Le jeudi 13 janvier 2011 à 17:35 +0100, Pablo Neira Ayuso a écrit :
> On 13/01/11 17:30, Pablo Neira Ayuso wrote:
> > On 13/01/11 15:39, Eric Dumazet wrote:
> >> Then, cluster match can be improved, I am sure you already have a patch
> >> for it.
> >
> > what scenario could benefit from the destination-based hashing?
>
> I'm telling this because it doesn't make too sense to me.
Me too ;)
But hash(source_IP, source_PORT) definitely make sense in some
workloads.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-01-13 16:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D2E1A74.5080102@netfilter.org>
2011-01-13 11:13 ` [PATCH] netfilter: ipt_CLUSTERIP: dont flood with "no conntrack!" Eric Dumazet
2011-01-13 11:23 ` Pablo Neira Ayuso
2011-01-13 11:28 ` Patrick McHardy
2011-01-13 11:29 ` Pablo Neira Ayuso
2011-01-13 11:36 ` Eric Dumazet
2011-01-13 11:32 ` Eric Dumazet
2011-01-13 11:54 ` Pablo Neira Ayuso
2011-01-13 13:38 ` [PATCH v4] netfilter: ipt_CLUSTERIP: remove " Eric Dumazet
2011-01-13 14:02 ` Jan Engelhardt
2011-01-13 14:39 ` Eric Dumazet
2011-01-13 16:30 ` Pablo Neira Ayuso
2011-01-13 16:35 ` Pablo Neira Ayuso
2011-01-13 16:48 ` Eric Dumazet [this message]
2011-01-18 15:28 ` 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=1294937329.3570.304.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--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