From: "minnie wu" <minniewkitty@yahoo.com.cn>
To: jchapman@katalix.com
Cc: netdev@oss.sgi.com
Subject: Re: How to improve small packet performance
Date: Thu, 14 Aug 2003 10:31:21 +0800 (CST) [thread overview]
Message-ID: <20030814023121.80893.qmail@web15212.mail.bjs.yahoo.com> (raw)
In-Reply-To: <1060835023.3f3b0ecfc97b4@webmail.katalix.com>
[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]
Here is the experimental setup I used:
A traffic generator[Smartbits] is sending from one of its ports to the PC on eth0. Linux routes the packet out eth1 back to the Smartbits. /proc/sys/net/ipv4/ip_forward set to 1.
The PC is a PIII 863MHz with 256M of RAM. And the NIC cards do not share the same irq.
The unidirectional test:
e100-v3.0.0dev12-napi 47k packets/sec
eepro100-napi-020619 89k packets/sec
minnie
jchapman@katalix.com wrote:I downloaded the eepro100 NAPI patch and tried it in my test setup (a
1GHz P-III configured as a 2-port bridge, 2.4.20-8 RH9 kernel). I see
e100-napi perform much better than eepro100, which is what I was
expecting
e100-v3.0.0dev12-napi 93k packets/sec
eepro100-napi-020619 49k packets/sec
When doing a bidirectional test, the eepro100 driver locks up
completely, although it seems to survive with 128 byte packets (where
the event rate is less).
What's your test setup? How are you generating your test traffic? Do
your NIC cards share the same irq?
-jc
---------------------------------
Do You Yahoo!?
暑期大片齐聚雅虎通 网络摄像头+雅虎通调频收音机等你来拿
[-- Attachment #2: Type: text/html, Size: 1546 bytes --]
next prev parent reply other threads:[~2003-08-14 2:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 4:23 How to improve small packet performance jchapman
2003-08-14 2:31 ` minnie wu [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-08 17:38 jchapman
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=20030814023121.80893.qmail@web15212.mail.bjs.yahoo.com \
--to=minniewkitty@yahoo.com.cn \
--cc=jchapman@katalix.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).