From: Jason Lunz <lunz@falooley.org>
To: netdev@oss.sgi.com
Subject: Re: [ANN] removal of certain net drivers coming soon: eepro100, xircom_tulip_cb, iph5526
Date: Sat, 29 Jan 2005 20:42:33 +0000 (UTC) [thread overview]
Message-ID: <ctgsfp$hpa$1@sea.gmane.org> (raw)
In-Reply-To: 41F952F4.7040804@pobox.com
["Followup-To:" header set to gmane.linux.kernel.]
jgarzik@pobox.com said:
> 3) eepro100
>
> Unmaintained; users should use e100.
>
> When I last mentioned eepro100 was going away, I got a few private
> emails saying complaining about issues not yet taken care of in e100.
> eepro100 will not be removed until these issues are resolved.
I have an intel eepro100 card in an old PII 266. With eepro100, it gets
~9Mbit, but e100 struggles to keep its head above 1Mbit, and is very
erratic.
Also, drivers/net/Kconfig still claims that E100_NAPI exists, but the
option to disable napi has long since been removed from the driver.
Jason
--- linux-2.6.10/drivers/net/Kconfig.pre 2005-01-29 15:40:48.000000000 -0500
+++ linux-2.6.10/drivers/net/Kconfig 2005-01-29 15:41:01.000000000 -0500
@@ -1435,23 +1435,6 @@
<file:Documentation/networking/net-modules.txt>. The module
will be called e100.
-config E100_NAPI
- bool "Use Rx Polling (NAPI)"
- depends on E100
- help
- NAPI is a new driver API designed to reduce CPU and interrupt load
- when the driver is receiving lots of packets from the card. It is
- still somewhat experimental and thus not yet enabled by default.
-
- If your estimated Rx load is 10kpps or more, or if the card will be
- deployed on potentially unfriendly networks (e.g. in a firewall),
- then say Y here.
-
- See <file:Documentation/networking/NAPI_HOWTO.txt> for more
- information.
-
- If in doubt, say N.
-
config LNE390
tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
depends on NET_PCI && EISA && EXPERIMENTAL
prev parent reply other threads:[~2005-01-29 20:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 20:45 [ANN] removal of certain net drivers coming soon: eepro100, xircom_tulip_cb, iph5526 Jeff Garzik
2005-01-27 21:07 ` Christoph Hellwig
2005-02-06 18:44 ` [2.6 patch] kill IPHASE5526 Adrian Bunk
2005-01-27 22:57 ` [ANN] removal of certain net drivers coming soon: eepro100, xircom_tulip_cb, iph5526 Russell King
2005-01-27 23:31 ` David S. Miller
2005-01-28 0:14 ` Russell King
2005-01-28 0:48 ` Lennert Buytenhek
2005-01-28 0:48 ` David S. Miller
2005-01-28 1:58 ` Scott Feldman
2005-01-28 5:22 ` David S. Miller
2005-01-28 9:33 ` [ANN] removal of certain net drivers coming soon: eepro100,?xircom_tulip_cb, iph5526 Meelis Roos
2005-01-28 19:11 ` Scott Feldman
2005-02-01 12:48 ` Meelis Roos
2005-02-01 18:57 ` Scott Feldman
2005-02-01 19:09 ` linux-os
2005-02-01 19:28 ` Scott Feldman
2005-01-29 8:17 ` [ANN] removal of certain net drivers coming soon: eepro100, xircom_tulip_cb, iph5526 Greg KH
2005-01-29 20:42 ` Jason Lunz [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='ctgsfp$hpa$1@sea.gmane.org' \
--to=lunz@falooley.org \
--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 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.