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!
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
