From: Patrick McHardy <kaber@trash.net>
To: Harald Welte <laforge@netfilter.org>
Cc: Henrik Nordstrom <hno@marasystems.com>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: ctnetlink questions
Date: Sun, 15 Feb 2004 11:01:10 +0100 [thread overview]
Message-ID: <402F4366.7020302@trash.net> (raw)
In-Reply-To: <20040214200326.GQ7756@sunbeam.de.gnumonks.org>
Harald Welte wrote:
> On Tue, Feb 10, 2004 at 01:39:01PM +0100, Patrick McHardy wrote:
>
>>but the other use for IDs was to continue an interrupted
>>dump at the right place, how can we solve this ? The problematic case
>>is when a single hash-chain doesn't fit into an skb. We need to remember
>>the last one dumped somehow, and be able to continue at the next one
>>not dumped even when the last one dumped is gone when the dump
>>continues.
>
>
> We'd have to ensure that a single hash chain is not longer than what we
> could put into one skb. This can be done by limiting the maximum number
> of entries in a bucket (and then rehash). Also, we should increase the
> default number of hash buckets to reduce the probability that this might
> happen.
I like the idea. So assuming that long hash chains are a result of "bad
luck" with the jenkins hash, we would just change the secret, rehash,
and repeat if some chains are still too long ? At what point do you
propose rehashing, at the moment the chain length exceeds some threshold
(or thereafter, defered to occur out of packet processing context), or
when dumping over netlink ?
>
> Also, Jozsef proposed a flip/flop bit mechanism that would solve that
> problem. What do you say to his proposal?
>
Can I find his proposal somewhere ?
>
>>Patrick
>
>
next prev parent reply other threads:[~2004-02-15 10:01 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031019171851.GR21521@sunbeam.de.gnumonks.org>
2003-10-19 19:36 ` ctnetlink questions Patrick McHardy
2003-10-19 20:28 ` Harald Welte
2003-10-19 22:55 ` Patrick McHardy
2003-10-20 1:05 ` Henrik Nordstrom
2003-10-20 3:01 ` Patrick McHardy
2003-10-20 3:09 ` Patrick McHardy
2003-10-20 6:34 ` Henrik Nordstrom
2003-10-20 17:53 ` Patrick McHardy
2003-10-20 7:15 ` Harald Welte
2003-10-20 9:37 ` Henrik Nordstrom
2003-10-20 18:43 ` Patrick McHardy
2003-10-20 18:37 ` Harald Welte
2003-10-20 19:17 ` Patrick McHardy
2003-10-20 19:41 ` Balazs Scheidler
2003-10-20 20:20 ` Patrick McHardy
2003-10-20 22:59 ` Harald Welte
2003-10-20 18:17 ` Patrick McHardy
2003-10-20 18:39 ` Harald Welte
2003-10-20 19:21 ` Patrick McHardy
2003-10-21 16:47 ` Patrick McHardy
2003-10-21 19:54 ` Henrik Nordstrom
2003-10-21 20:00 ` Patrick McHardy
2003-10-20 18:52 ` Harald Welte
2003-10-20 19:52 ` Patrick McHardy
2003-10-20 23:09 ` Harald Welte
2003-10-20 7:04 ` Harald Welte
2003-10-20 7:17 ` Jozsef Kadlecsik
2003-10-20 9:29 ` Henrik Nordstrom
2004-02-06 18:52 ` Harald Welte
2004-02-09 10:33 ` Pablo Neira
2004-02-10 12:39 ` Patrick McHardy
2004-02-14 20:03 ` Harald Welte
2004-02-15 10:01 ` Patrick McHardy [this message]
2004-02-17 21:37 ` Harald Welte
2003-10-20 14:48 ` Harald Welte
2003-10-20 18:53 ` Patrick McHardy
2003-10-20 22:57 ` Harald Welte
2003-10-20 11:11 ` Jozsef Kadlecsik
2003-10-20 6:58 ` Harald Welte
2003-10-19 14:54 Harald Welte
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=402F4366.7020302@trash.net \
--to=kaber@trash.net \
--cc=hno@marasystems.com \
--cc=kadlec@blackhole.kfki.hu \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.