Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265806AbUFDPY1 (ORCPT ); Fri, 4 Jun 2004 11:24:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265803AbUFDPY1 (ORCPT ); Fri, 4 Jun 2004 11:24:27 -0400 Received: from hermes.fachschaften.tu-muenchen.de ([129.187.202.12]:48101 "HELO hermes.fachschaften.tu-muenchen.de") by vger.kernel.org with SMTP id S265806AbUFDPX7 (ORCPT ); Fri, 4 Jun 2004 11:23:59 -0400 Date: Fri, 4 Jun 2004 17:23:52 +0200 From: Adrian Bunk To: jgarzik@pobox.com Cc: linux-net@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [2.6 patch] add NAPI help texts Message-ID: <20040604152352.GB7744@fs.tum.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 6066 Lines: 180 NAPI seems to be so self-explaining that no help texts are needed. ;-) I combined the two help texts that were at NAPI options, and added them to all NAPI options. diffstat output: drivers/net/Kconfig | 84 +++++++++++++++++++++++++++++++++++++- drivers/net/tulip/Kconfig | 15 ++++-- 2 files changed, 94 insertions(+), 5 deletions(-) Please apply Adrian --- linux-2.6.7-rc2-mm2-full/drivers/net/Kconfig.old 2004-06-04 17:10:43.000000000 +0200 +++ linux-2.6.7-rc2-mm2-full/drivers/net/Kconfig 2004-06-04 17:18:14.000000000 +0200 @@ -1237,6 +1237,19 @@ config AMD8111E_NAPI bool "Enable NAPI support" depends on AMD8111_ETH + 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 for more + information. + + If in doubt, say N. config ADAPTEC_STARFIRE tristate "Adaptec Starfire/DuraLAN support" @@ -1264,6 +1277,11 @@ deployed on potentially unfriendly networks (e.g. in a firewall), then say Y here. + See for more + information. + + If in doubt, say N. + config AC3200 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)" depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL @@ -1451,6 +1469,19 @@ 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 for more + information. + + If in doubt, say N. config LNE390 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)" @@ -1924,6 +1955,19 @@ config E1000_NAPI bool "Use Rx Polling (NAPI)" depends on E1000 + 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 for more + information. + + If in doubt, say N. config MYRI_SBUS tristate "MyriCOM Gigabit Ethernet support" @@ -1983,8 +2027,20 @@ config R8169_NAPI bool "Use Rx and Tx Polling (NAPI) (EXPERIMENTAL)" - depends on R8169 && EXPERIMENTAL + depends on R8169 && EXPERIMENTAL + 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 for more + information. + + If in doubt, say N. config SK98LIN tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support" @@ -2114,6 +2170,19 @@ config IXGB_NAPI bool "Use Rx Polling (NAPI) (EXPERIMENTAL)" depends on IXGB && EXPERIMENTAL + 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 for more + information. + + If in doubt, say N. config S2IO tristate "S2IO 10Gbe XFrame NIC" @@ -2126,6 +2195,19 @@ config S2IO_NAPI bool "Use Rx Polling (NAPI) (EXPERIMENTAL)" depends on S2IO && EXPERIMENTAL + 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 for more + information. + + If in doubt, say N. endmenu --- linux-2.6.7-rc2-mm2-full/drivers/net/tulip/Kconfig.old 2004-06-04 17:14:18.000000000 +0200 +++ linux-2.6.7-rc2-mm2-full/drivers/net/tulip/Kconfig 2004-06-04 17:16:07.000000000 +0200 @@ -71,10 +71,17 @@ config TULIP_NAPI bool "Use NAPI RX polling " depends on TULIP - ---help--- - This is of useful for servers and routers dealing with high network loads. - - See . + 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 for more + information. If in doubt, say N. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/