From: Filip Sneppe <filip.sneppe@cronos.be>
To: SB CH <chulmin2@hotmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: connection tracking and keepalive
Date: 15 Jan 2003 13:44:00 +0100 [thread overview]
Message-ID: <1042634640.923.27.camel@xbox> (raw)
In-Reply-To: <F32yuH5stQqOPsNtP3U00008bbd@hotmail.com>
Hi,
On Wed, 2003-01-15 at 12:37, SB CH wrote:
> Hello,
>
> Does connection tracking has a relation with the keepalive config at
> httpd.conf?
No, not really.
>
> I would like that connection tracking has a relation with keepalive or not?
Connection tracking is more related to TCP states. Obviously with
keepalives off, every request requires a new TCP connection, so
indirectly they are related through the TCP states.
> and how much memory size is required to execute connection tracking ?
384 bytes per connection (may be slightly different depending on
your kernelversion - see /proc/slabinfo, ip_conntrack entry) +
a couple of bytes per hash (I think 8 bytes) * hashsize (determined
when ip_conntrack is loaded)
Regards,
Filip
prev parent reply other threads:[~2003-01-15 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 11:37 connection tracking and keepalive SB CH
2003-01-15 12:44 ` Filip Sneppe [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=1042634640.923.27.camel@xbox \
--to=filip.sneppe@cronos.be \
--cc=chulmin2@hotmail.com \
--cc=netfilter@lists.netfilter.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