From: Mayuresh Chitale <mchitale@gmail.com>
To: netdev@vger.kernel.org, netfilter@lists.netfilter.org
Subject: does routing performance degrade from 2.4.20 to 2.4.31 ?
Date: Thu, 10 Nov 2005 16:12:29 +0600 [thread overview]
Message-ID: <d096a3ee0511100212o6742f5a0t608c63cc9a35d8ae@mail.gmail.com> (raw)
Hi All,
We are working on kernel version 2.4.20 and are trying to migrate to
version 2.4.31. We are doing some performance related tests to see the
impact of migration. The routing throughput seems to degrade from
2.4.20 to 2.4.31.
We have a Malta board with mips 4kc processor and are using iperf tool
to do the testing. Two test PCs are connected to the malta and iperf
server is run on PC and the client on another PC. With netfilter
compiled into the kernel, version 2.4.20 shows better result than
2.4.31. No rules except the default (all accept) have been applied.
Without netfilter, both perform almost identical. Is this expected ??
The dump below shows the measurements. If anyone has done similar
tests before, please share with me their results.
Have a nice day.
Mayuresh.
2.4.31
=====
[mayuresh@localhost ~]$ ./iperf -c 100.0.0.1 -P 2
------------------------------------------------------------
Client connecting to 100.0.0.1, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[ 4] local 10.1.1.99 port 33702 connected with 100.0.0.1 port 5001
[ 3] local 10.1.1.99 port 33701 connected with 100.0.0.1 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 16.9 MBytes 14.2 Mbits/sec
[ 4] 0.0-10.0 sec 17.0 MBytes 14.2 Mbits/sec
[SUM] 0.0-10.0 sec 33.9 MBytes 28.3 Mbits/sec
2.4.20
=====
[mayuresh@localhost ~]$ ./iperf -c 100.0.0.1 -P 2
------------------------------------------------------------
Client connecting to 100.0.0.1, TCP port 5001
TCP window size: 16.0 KByte (default)
------------------------------------------------------------
[ 4] local 10.1.1.99 port 33705 connected with 100.0.0.1 port 5001
[ 3] local 10.1.1.99 port 33704 connected with 100.0.0.1 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 20.2 MBytes 16.9 Mbits/sec
[ 4] 0.0-10.0 sec 20.2 MBytes 16.9 Mbits/sec
[SUM] 0.0-10.0 sec 40.4 MBytes 33.8 Mbits/sec
reply other threads:[~2005-11-10 10:12 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=d096a3ee0511100212o6742f5a0t608c63cc9a35d8ae@mail.gmail.com \
--to=mchitale@gmail.com \
--cc=netdev@vger.kernel.org \
--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