From: Patrick Schaaf <bof@bof.de>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Andi Kleen <ak@suse.de>, Harald Welte <laforge@gnumonks.org>,
Netfilter Mailing List <netfilter-devel@lists.netfilter.org>,
Linux Kernel mailing list <linux-kernel@vger.kernel.org>,
Patrick Schaaf <bof@bof.de>
Subject: Re: ip_conntrack_hash() problem
Date: Thu, 5 Sep 2002 08:51:03 +0200 [thread overview]
Message-ID: <20020905085103.G19551@oknodo.bof.de> (raw)
In-Reply-To: <20020905044436.0772A2C0DF@lists.samba.org>; from rusty@rustcorp.com.au on Thu, Sep 05, 2002 at 10:39:40AM +1000
Rusty,
> This work is already done:
> http://www.kernel.org/pub/linux/kernel/people/rusty/patches/Netfilter/conntrack_hashing.patch.gz
Regarding the rehash check in ip_conntrack_find_get, wouldn't it be
better to do that in the confirm function, where a new conntrack
is put into the list? That's called a lot less often than _find_get,
and should be logically equivalent. IOW, why wait until we _find_
an overly long list, when we can rehash at the point in time when
it _became_ overly long?
best regards
Patrick
next prev parent reply other threads:[~2002-09-05 6:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 12:33 Martin Wilck
2002-09-04 12:56 ` Harald Welte
2002-09-04 13:24 ` Martin Wilck
2002-09-04 13:26 ` Andi Kleen
2002-09-05 0:39 ` Rusty Russell
2002-09-05 6:21 ` Patrick Schaaf
2002-09-05 6:24 ` David S. Miller
2002-09-05 6:33 ` Patrick Schaaf
2002-09-05 6:32 ` David S. Miller
2002-09-05 6:39 ` Patrick Schaaf
2002-09-05 6:40 ` David S. Miller
2002-09-05 13:37 ` Rik van Riel
2002-09-05 11:14 ` Rusty Russell
2002-09-05 6:51 ` Patrick Schaaf [this message]
2002-09-05 7:19 ` Martin Wilck
2002-09-05 11:15 ` Rusty Russell
2002-09-05 11:54 ` Andi Kleen
2002-09-05 17:55 ` Patrick Schaaf
2002-09-05 18:24 ` Martin Wilck
2002-09-05 8:19 ` Harald Welte
2002-09-04 13:40 ` Martin Wilck
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=20020905085103.G19551@oknodo.bof.de \
--to=bof@bof.de \
--cc=ak@suse.de \
--cc=laforge@gnumonks.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=rusty@rustcorp.com.au \
/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
all inboxes | Powered by JetHome®