All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Padovan <evcz@evcz.tk>
To: netfilter@vger.kernel.org
Subject: hashlimit performance (--hashlimit-htable-size value)
Date: Wed, 11 Apr 2012 10:44:39 +0200	[thread overview]
Message-ID: <4F854477.5070701@evcz.tk> (raw)

Hi,

how far can I push --hashlimit-htable-max size?

I did some tests with 262144:
-m hashlimit --hashlimit-mode srcip --hashlimit-name testlimiter
--hashlimit 1/s --hashlimit-burst 10 --hashlimit-htable-size 4096
--hashlimit-htable-max 262144 -j RETURN

but it wasn't holding:

xxxx:11:05 white kernel: xt_hashlimit: max count of 262144 reached
xxxx:11:05 white kernel: xt_hashlimit: max count of 262144 reached
xxxx:11:05 white kernel: xt_hashlimit: max count of 262144 reached
xxxx:11:05 white kernel: xt_hashlimit: max count of 262144 reached
xxxx:11:05 white kernel: xt_hashlimit: max count of 262144 reached
xxxx:11:05 white kernel: xt_hashlimit: max count of 262144 reached
xxxx:11:05 white kernel: xt_hashlimit: max count of 262144 reached
xxxx:11:05 white kernel: xt_hashlimit: max count of 262144 reached
xxxx:11:05 white kernel: xt_hashlimit: max count of 262144 reached
xxxx:11:10 white kernel: net_ratelimit: 239072 callbacks suppressed
xxxx:11:10 white kernel: xt_hashlimit: max count of 262144 reached
xxxx:11:10 white kernel: xt_hashlimit: max count of 262144 reached

Am I doing it wrong?

Should I set hashlimit-htable-size = hashlimit-htable-max in order to
achieve better performance and map 1 IP to 1 bucket?

I even tried to take a look at the module source code but I'm not
skilled enough to fully understand it :D

I'm asking if there is some in-depth documentation about how
hashlimit-htable-max interact with the other
parameters(--hashlimit-htable-expire & --hashlimit-htable-gcinterval) in
order to handle high traffic flows or if anyone got real world
experience taking hashlimit to the limit :)

Thank you


                 reply	other threads:[~2012-04-11  8:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4F854477.5070701@evcz.tk \
    --to=evcz@evcz.tk \
    --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 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.