From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Zhang Fuxin <fxzhang@ict.ac.cn>
Cc: linux-mips@oss.sgi.com, saw@saw.sw.com.sg,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: NAPI for eepro100
Date: Wed, 12 Jun 2002 19:00:00 -0400 [thread overview]
Message-ID: <ae8k4b$4t0$2@main.gmane.org> (raw)
In-Reply-To: 3D0740ED.2060907@ict.ac.cn
Zhang Fuxin wrote:
> hi,all
> Recently i've converted eepro100 driver to use napi,in order to improve
> network performance of my poor 150M mips machine. It does eliminate
> the interrupt live lock seen before,maintaining a peak throughput under
> heavy load.
> In case anybody are interested,i post the patches to the list. They are
> 3 incremental patchs:
> eepro100-napi.patch is against 2.5.20 eepro100.c and provide basic
> napi support
Nifty, I'll take a look at this.
> eepro100-proc.patch is proc file system support adapted from intel's
> e100 driver. I am using it for debugging.
> eepro100-mips.patch is mips specific patch to make it work(well) for
> my mips
> platform.
Just FWIW I'm not gonna apply these... for the 'proc' patch, that either
needs to be moved to ethtool, or we should make a filesystem for net
drivers that exports procfs-like inodes. for the 'mips' patch, it looks
like the arch maintainer(s) need to fix the PCI DMA support...
Jeff
prev parent reply other threads:[~2002-06-12 23:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-12 12:39 NAPI for eepro100 Zhang Fuxin
2002-06-12 23:00 ` Jeff Garzik
2002-06-12 23:05 ` David S. Miller
2002-06-12 23:05 ` David S. Miller
2002-06-12 23:17 ` Jeff Garzik
2002-06-12 23:17 ` Jeff Garzik
2002-06-12 23:33 ` David S. Miller
2002-06-12 23:33 ` David S. Miller
2002-06-13 2:25 ` Donald Becker
2002-06-13 2:25 ` Donald Becker
2002-06-13 7:15 ` Samuel Maftoul
2002-06-19 11:46 ` Bill Davidsen
2002-06-13 2:25 ` Donald Becker
2002-06-12 23:33 ` David S. Miller
2002-06-13 8:57 ` Andrey Savochkin
2002-06-13 8:47 ` David S. Miller
2002-06-13 8:47 ` David S. Miller
2002-06-13 8:47 ` David S. Miller
2002-06-13 8:57 ` Andrey Savochkin
2002-06-12 23:05 ` David S. Miller
2002-06-12 23:00 ` Jeff Garzik [this message]
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='ae8k4b$4t0$2@main.gmane.org' \
--to=jgarzik@mandrakesoft.com \
--cc=fxzhang@ict.ac.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@oss.sgi.com \
--cc=netdev@oss.sgi.com \
--cc=saw@saw.sw.com.sg \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.