From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter@vger.kernel.org
Subject: Re: [ANNOUNCE] ipset 6.5 released
Date: Tue, 17 May 2011 12:03:11 +0100 [thread overview]
Message-ID: <4DD255EF.1040209@googlemail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1105170941590.31848@blackhole.kfki.hu>
>> That's great news! Should I assume that the (more-than-double) hash bug I
>> reported a while ago has also been fixed?
>>
>
> Yes, it was fixed, the last one ("Fix adding ranges to hash types") covers
> that.
>
Thank you Jozsef.
I have quickly tried the new version last night on a freshly compiled
kernel (with ipset kernel modules included into the kernel - not as
modules though) - the loading performance of "bulk" ranges is much, much
better now, though I've got an error when trying to load a set which
consisted of just 3 different subnet ranges (that set was using the
"old" treemap syntax). When I have some more time - probably later this
evening - I will post details of that error (I think it was to do with
hashes again).
Also, I don't know whether you will be interested in this, but when I
modified ipset 4.5 in order to split the kernel modules from the
userspace tool and include these in two separate building streams for my
systems, I managed to change ipset 4.5 to enable the use of
autogen/automake tools and then the execution of "./configure" as part
of building that package. As part of that process I introduced 2 extra
"parameters" to it - "--hash-size" and "--max-elements". I could send
you this patch to "refresh" the ipset 4.5 version or just have a look at
it, if you so desire - just let me know. ipset 4.5 has served me very
well since I started using it and was a vital contributor to the
improved stability and performance on all my systems.
next prev parent reply other threads:[~2011-05-17 11:03 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-15 13:50 [ANNOUNCE] ipset 6.5 released Jozsef Kadlecsik
2011-05-16 15:41 ` Mr Dash Four
2011-05-17 7:42 ` Jozsef Kadlecsik
2011-05-17 11:03 ` Mr Dash Four [this message]
2011-05-17 11:51 ` Jozsef Kadlecsik
2011-05-17 15:23 ` Mr Dash Four
2011-05-17 18:36 ` Mr Dash Four
2011-05-18 7:54 ` Jozsef Kadlecsik
2011-05-18 10:59 ` Mr Dash Four
2011-05-18 11:22 ` Jozsef Kadlecsik
2011-05-21 19:42 ` Mr Dash Four
2011-05-21 19:45 ` Jozsef Kadlecsik
2011-05-21 19:58 ` Jozsef Kadlecsik
2011-05-21 20:11 ` Mr Dash Four
2011-05-21 21:31 ` Jozsef Kadlecsik
2011-05-21 21:33 ` Jan Engelhardt
2011-05-21 21:41 ` Mr Dash Four
2011-05-21 21:52 ` Jan Engelhardt
2011-05-21 23:08 ` Jozsef Kadlecsik
2011-05-22 1:01 ` Mr Dash Four
2011-05-22 10:05 ` Jozsef Kadlecsik
2011-05-22 10:36 ` Jozsef Kadlecsik
2011-05-22 11:44 ` Mr Dash Four
2011-05-22 11:44 ` Mr Dash Four
2011-05-22 21:21 ` Jozsef Kadlecsik
2011-05-22 21:32 ` Mr Dash Four
2011-05-22 15:00 ` Jan Engelhardt
2011-05-22 13:57 ` Mr Dash Four
2011-05-22 14:05 ` Mr Dash Four
2011-05-21 21:51 ` Mr Dash Four
2011-05-21 21:41 ` Mr Dash Four
2011-05-21 22:28 ` Jozsef Kadlecsik
2011-05-21 22:41 ` Jozsef Kadlecsik
2011-05-21 22:44 ` Mr Dash Four
2011-05-21 22:42 ` Mr Dash Four
2011-05-22 14:52 ` Mr Dash Four
2011-05-21 22:15 ` Mr Dash Four
2011-05-21 22:31 ` Jozsef Kadlecsik
2011-05-21 22:42 ` Mr Dash Four
2011-05-21 22:49 ` Jozsef Kadlecsik
2011-05-21 22:57 ` Mr Dash Four
2011-05-21 23:25 ` Jozsef Kadlecsik
2011-05-21 23:33 ` Mr Dash Four
2011-05-22 9:56 ` Jozsef Kadlecsik
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=4DD255EF.1040209@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter@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).