From: Dennis Jacobfeuerborn <dennisml@conversis.de>
To: "Remzi AKYÜZ" <linuxliste@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: conntrack table limits
Date: Wed, 26 Jan 2011 03:06:52 +0100 [thread overview]
Message-ID: <4D3F81BC.7020600@conversis.de> (raw)
In-Reply-To: <4D3ED4D6.6000601@gmail.com>
On 01/25/2011 02:49 PM, Remzi AKYÜZ wrote:
> /etc/modules
> nf_conntrack acct=1 hashsize=1048576
>
> Hashsize calc;
>
> HASHSIZE = CONNTRACK_MAX / 8 = RAMSIZE (in bytes) / 131072 = RAMSIZE (in
> MegaBytes) * 8
> HASHSIZE = CONNTRACK_MAX / 8 = RAMSIZE (in bytes) / 131072 / (x / 32)
> x= 32 or 64
>
> CONNTRACK_MAX = HASHSIZE * 8
That makes sense, thanks.
> you can see this
> http://antmeetspenguin.blogspot.com/2011/01/high-performance-linux-router.html
> page.
>
> On 01/25/2011 01:45 PM, Dennis Jacobfeuerborn wrote:
>> Hi,
>> I'm trying to find out how high I can set conntrack_max on a 2GB 64 bit
>> system. On the net I found different ways of calculating this but they
>> seem to end up with different results. One forumla tells me that I can
>> fit a maximum of 65535 connections into 2GB of RAM but the other says
>> that with 304 bytes per connection (plus a bit of slab allocation
>> overhead) I can easily fit more than a million connections into the table.
>> Also even with the current limit 65535 and the table having ca. 30.000
>> entries I've almost 1.8GB ram free/cached which leads me to believe the
>> second way of calculating this is more accurate.
>> What is the proper way to calculate this?
>>
>> Regards,
>> Dennis
>> --
>> To unsubscribe from this list: send the line "unsubscribe netfilter" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2011-01-26 2:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 11:45 conntrack table limits Dennis Jacobfeuerborn
2011-01-25 13:49 ` Remzi AKYÜZ
2011-01-26 2:06 ` Dennis Jacobfeuerborn [this message]
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=4D3F81BC.7020600@conversis.de \
--to=dennisml@conversis.de \
--cc=linuxliste@gmail.com \
--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.