From: Harald Welte <laforge@netfilter.org>
To: Carlos Carvalho <carlos@fisica.ufpr.br>
Cc: netdev@oss.sgi.com
Subject: Re: Memory usage for ip_conntrack
Date: Thu, 24 Jul 2003 18:01:16 +0200 [thread overview]
Message-ID: <20030724160107.GC10897@naboo> (raw)
In-Reply-To: <16153.56832.379224.202834@fisica.ufpr.br>
[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]
On Sat, Jul 19, 2003 at 09:10:40PM -0300, Carlos Carvalho wrote:
> Martin Josefsson (gandalf@wlug.westbo.se) wrote on 18 July 2003 23:28:
> >> If I echo 102400 > /proc/sys/net/ipv4/ip_conntrack_max, what is my worst
> >> case memory usage?
> >
> >Don't do this. This will increase the maximum number of connections it
> >will track, but not the number of buckets. Which means that it will be
> >slower due to longer collision-chains. Instead increase the number of
> >buckets. modprobe ip_conntrack hashsize=131072 (or any number here.
>
> How can we increase the number of buckets with a monolithic kernel?
For 2.4: by altering the default in the kernel source, sorry.
For 2.5/2.6: there is now a generic way of specifying module parameters
from the boot command line.
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-07-24 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 20:07 Memory usage for ip_conntrack Dax Kelson
2003-07-18 21:28 ` Martin Josefsson
2003-07-19 0:12 ` Memory usage/tuning " Dax Kelson
2003-07-20 0:10 ` Memory usage " Carlos Carvalho
2003-07-24 16:01 ` Harald Welte [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=20030724160107.GC10897@naboo \
--to=laforge@netfilter.org \
--cc=carlos@fisica.ufpr.br \
--cc=netdev@oss.sgi.com \
/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.