From: "Mayuresh Chitale" <mchitale@gmail.com>
To: netdev@vger.kernel.org, linux-net@vger.kernel.org
Subject: Linux 2.6 Vs linux 2.4 routing
Date: Sat, 17 Jun 2006 00:11:19 +0530 [thread overview]
Message-ID: <d096a3ee0606161141n3c481ed9kfcbf70af7393affa@mail.gmail.com> (raw)
Hi All,
I am doing a routing test using linux 2.4 and linux 2.6 kernel on our
board. I am using 2.4.31 and 2.6.16.17 for comparison.
I have ported the bsp and drivers from 2.4 to 2.6 and am using a
smartbits tester which pumps traffic at high rates and at varying
packet sizes.
On 2.4, the test goes fine ie I get meaningful values. But on 2.6
kernel, routing begins and continues for sometime before it completely
stops. The smartbits configuration is identical in both the cases.
I have noticed same problem with dlink and 3com cards which is causing
me to suspect that there is some probem with 2.6 routing.
Has anyone seen a similar problem ?
Any inputs on this would be appreciated.
Thanks,
Mayuresh.
next reply other threads:[~2006-06-16 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 18:41 Mayuresh Chitale [this message]
2006-06-17 10:33 ` Linux 2.6 Vs linux 2.4 routing Krzysztof Oledzki
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=d096a3ee0606161141n3c481ed9kfcbf70af7393affa@mail.gmail.com \
--to=mchitale@gmail.com \
--cc=linux-net@vger.kernel.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox