From: jchapman@katalix.com
To: minniewkitty@yahoo.com.cn
Cc: netdev@oss.sgi.com
Subject: Re: How to improve small packet performance
Date: Wed, 13 Aug 2003 23:23:43 -0500 [thread overview]
Message-ID: <1060835023.3f3b0ecfc97b4@webmail.katalix.com> (raw)
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
minnie wu wrote:
> Hi, all!
> I tried e100-napi, but it's performance is still worse than
> eepro100-napi. It seems that napi cannot meet my needs. Any ideas?
>
> jchapman@katalix.com wrote:
>
> > Try the latest e100 development driver from sf.net/projects/e1000.
> > Make >sure you compile it with NAPI enabled.
>
> minnie wu wrote:
>
> > Hi, all!
> > I'm working on e100/eepro100, kernel version 2.4.20. I
> > used NAPI, but the 64 byte small packet dual throughout
> > is only 28M/s. How to improve small packet performance further?
>
-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
next reply other threads:[~2003-08-14 4:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 4:23 jchapman [this message]
2003-08-14 2:31 ` How to improve small packet performance minnie wu
-- 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=1060835023.3f3b0ecfc97b4@webmail.katalix.com \
--to=jchapman@katalix.com \
--cc=minniewkitty@yahoo.com.cn \
--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).