From: Patrick McHardy <kaber@trash.net>
To: Andy Polyakov <appro@fy.chalmers.se>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: iptables performance under 2.6.0[-test9]
Date: Tue, 28 Oct 2003 09:30:36 +0100 [thread overview]
Message-ID: <3F9E292C.3020509@trash.net> (raw)
In-Reply-To: <3F9D5E60.866B0B63@fy.chalmers.se>
Can you please provide (pcap format) packet dumps of
a) the correct situation
b) broken situation
I would like to have a look at it. Please make sure to capture
with "-s 1500" so the packets are in the dump completly.
Thanks,
Patrick
Andy Polyakov wrote:
>>I tried to deploy 2.6.0[-test9] iptables to masquerade a private
>>interace. Strangely enough ip_conntrack.ko module seems to affect
>>performance of *some* TCP connections. ... I'm looking for
>>triggering factors...
>>
>>
>
>Apparently it's not certain connections as wholes which are affected,
>but only some outgoing packets. Those packets corresponding to socket
>writes larger than MTU-40 [where 40 is size of TCP/IP header]... I fail
>to imagine how come, but here is how I can reproduce the problem with
>attached head.pl script:
>
>- 'lsmod' to make sure *no* iptables modules are loaded;
>- 'time ./head.pl some.host 2000' says that it takes a portion of
>elapsed second for script to complete;
>- modprobe ip_conntrack;
>- 'time ./head.pl some.host 2000' now says that it takes over 3(!)
>elapsed seconds to complete;
>
>If I reduce amount of \n's send in first socket write by passing value
>of 1460 or lower as the last command-line argument, the script completes
>instantly regardless if ip_conntrack is loaded or not. Therefore the
>conclusion about MTU-40... Cheers. A.
>
next prev parent reply other threads:[~2003-10-28 8:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 16:10 iptables performance under 2.6.0[-test9] Andy Polyakov
2003-10-27 18:05 ` Andy Polyakov
2003-10-27 18:30 ` Andy Polyakov
2003-10-28 8:30 ` Patrick McHardy [this message]
2003-10-28 10:01 ` Andy Polyakov
2003-10-28 10:09 ` Patrick McHardy
2003-10-28 11:18 ` Andy Polyakov
2003-10-28 12:19 ` Patrick McHardy
2003-10-28 21:59 ` Andy Polyakov
2003-10-29 0:32 ` Patrick McHardy
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=3F9E292C.3020509@trash.net \
--to=kaber@trash.net \
--cc=appro@fy.chalmers.se \
--cc=netfilter-devel@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 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.