From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: Pawe? Krawczyk <kravietz@aba.krakow.pl>
Cc: zhengchuanbo <zhengcb@netpower.com.cn>,
"linux-kernel @ vger. kernel. org" <linux-kernel@vger.kernel.org>
Subject: Re: about the tuning of eepro100
Date: Sat, 10 Aug 2002 18:55:58 +0100 [thread overview]
Message-ID: <20020810185558.C306@kushida.apsleyroad.org> (raw)
In-Reply-To: <20020810095126.GF21239@aba.krakow.pl>; from kravietz@aba.krakow.pl on Sat, Aug 10, 2002 at 11:51:26AM +0200
Pawe? Krawczyk wrote:
> > so i think the limit is at the eepro100 card. is there any way to
> > improve the throughput? or someone got a higher throughput then
> > that? the eepro100 chip is 82559.
>
> Use e100 driver from Intel [1] with the following parameters:
>
> insmod e100.o BundleSmallFr=1 IntDelay=0x600 ucode=1
>
> Intel's driver supports all the interrupt saving features (interrupt
> delay and small packet bundling) present in EEPro/100 cards. The driver
> is now GPL, so it should get back to the mainstream kernel.
I don't think you will get better than 90% performance, but if you do
please let me know! I have written another e100 driver, in an attempt
to transmit and receive small packets at the maximum possible rate.
In tests, it would not even transmit at 100% small packets on our 82558.
(I didn't do that test on our 82559).
Ah well..
Curiously, I found that turning on the interrupt saving microcode slows
the cards down. It lessens the load on the mainboard CPU, but I am not
using interrupts, I'm polling the memory descriptors 100% of the time,
so the interrupt saving microcode shouldn't affect the mainboard CPU.
It does lower the throughput though.
-- Jamie
next prev parent reply other threads:[~2002-08-10 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-10 9:38 about the tuning of eepro100 zhengchuanbo
2002-08-10 9:51 ` Paweł Krawczyk
2002-08-10 10:09 ` Adrian Bunk
2002-08-10 17:55 ` Jamie Lokier [this message]
2002-08-10 18:02 ` Paweł Krawczyk
2002-08-10 18:18 ` Jeff Garzik
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=20020810185558.C306@kushida.apsleyroad.org \
--to=lk@tantalophile.demon.co.uk \
--cc=kravietz@aba.krakow.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=zhengcb@netpower.com.cn \
/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