From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [ANNOUNCE] ipset 6.6 released
Date: Tue, 24 May 2011 13:22:51 +0100 [thread overview]
Message-ID: <4DDBA31B.4040406@googlemail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1105241404390.1846@blackhole.kfki.hu>
> Currently I can suggest you that tune both the hashsize and maxelem
> parameters: the hashsize tells the system the initial hash size (and thus
> the used memory resource) while maxelem tells up to what number of
> elements can be added to the set. You are free to enter quite high maxelem
> values, it does not waste memory. As you add more and more elements, the
> hash size is increased from the one specified by 'hashsize'. But you (or
> the SET targets) can't add more elements than "maxelem".
>
> When you save a set, the current hashsize is saved and not the one
> specified at set creation time.
>
Ah, I see! So maxelem does not have an impact on system resources as
hashsize has, is that right? If that is the case, then I may as well
leave the default (64k) as I'd never exceed this value. Thanks for your
input, as always!
next prev parent reply other threads:[~2011-05-24 12:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 8:48 [ANNOUNCE] ipset 6.6 released Jozsef Kadlecsik
2011-05-24 11:09 ` Mr Dash Four
2011-05-24 11:44 ` Jozsef Kadlecsik
2011-05-24 11:54 ` Mr Dash Four
2011-05-24 12:19 ` Jozsef Kadlecsik
2011-05-24 12:22 ` Mr Dash Four [this message]
2011-05-24 12:31 ` Jozsef Kadlecsik
2011-05-25 2:33 ` Mr Dash Four
2011-05-25 1:58 ` Mr Dash Four
2011-05-25 7:23 ` Jozsef Kadlecsik
2011-05-25 8:32 ` Mr Dash Four
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=4DDBA31B.4040406@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@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).