From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net
To: davem@davemloft.net
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
netdev@vger.kernel.org, gospo@redhat.com, bphilips@novell.com
Subject: [PATCH 01/27] Documentation/networking/e1000.txt: Update documentation
Date: Fri, 10 Dec 2010 22:16:55 -0800 [thread overview]
Message-ID: <1292048241-22026-2-git-send-email-jeffrey.t.kirsher@intel.com> (raw)
In-Reply-To: <1292048241-22026-1-git-send-email-jeffrey.t.kirsher@intel.com>
Update Intel Wired LAN e1000 documentation.
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
---
Documentation/networking/e1000.txt | 10 +++++-----
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/networking/e1000.txt b/Documentation/networking/e1000.txt
index d9271e7..6cb13e9 100644
--- a/Documentation/networking/e1000.txt
+++ b/Documentation/networking/e1000.txt
@@ -79,7 +79,7 @@ InterruptThrottleRate
---------------------
(not supported on Intel(R) 82542, 82543 or 82544-based adapters)
Valid Range: 0,1,3,4,100-100000 (0=off, 1=dynamic, 3=dynamic conservative,
- 4=simplified balancing)
+ 4=simplified balancing)
Default Value: 3
The driver can limit the amount of interrupts per second that the adapter
@@ -124,8 +124,8 @@ InterruptThrottleRate is set to mode 1. In this mode, which operates
the same as mode 3, the InterruptThrottleRate will be increased stepwise to
70000 for traffic in class "Lowest latency".
-In simplified mode the interrupt rate is based on the ratio of Tx and
-Rx traffic. If the bytes per second rate is approximately equal, the
+In simplified mode the interrupt rate is based on the ratio of TX and
+RX traffic. If the bytes per second rate is approximately equal, the
interrupt rate will drop as low as 2000 interrupts per second. If the
traffic is mostly transmit or mostly receive, the interrupt rate could
be as high as 8000.
@@ -245,7 +245,7 @@ NOTE: Depending on the available system resources, the request for a
TxDescriptorStep
----------------
Valid Range: 1 (use every Tx Descriptor)
- 4 (use every 4th Tx Descriptor)
+ 4 (use every 4th Tx Descriptor)
Default Value: 1 (use every Tx Descriptor)
@@ -312,7 +312,7 @@ Valid Range: 0-xxxxxxx (0=off)
Default Value: 256
Usage: insmod e1000.ko copybreak=128
-Driver copies all packets below or equaling this size to a fresh Rx
+Driver copies all packets below or equaling this size to a fresh RX
buffer before handing it up the stack.
This parameter is different than other parameters, in that it is a
--
1.7.3.2
next prev parent reply other threads:[~2010-12-11 6:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-11 6:16 [net-next 00/27][pull-request] Intel Wired LAN Driver Updates Jeff Kirsher
2010-12-11 6:16 ` Jeff Kirsher [this message]
2010-12-11 6:16 ` [PATCH 02/27] Documentation/networking/e1000e.txt: Update documentation Jeff Kirsher
2010-12-11 6:16 ` [PATCH 03/27] Documentation/networking/igb.txt: update documentation Jeff Kirsher
2010-12-11 6:16 ` [PATCH 04/27] Documentation/networking/igbvf.txt: Update documentation Jeff Kirsher
2010-12-11 6:34 ` Ben Hutchings
[not found] ` <AANLkTikUqZsaSg-q+GJvRrUb4C8rFZSbBta0tyeh==Ay@mail.gmail.com>
2010-12-11 19:44 ` David Miller
2010-12-11 6:16 ` [PATCH 05/27] Documentation/networking/ixgbe.txt: Update ixgbe documentation Jeff Kirsher
2010-12-11 6:17 ` [PATCH 06/27] Documentation/networking/ixgbevf.txt: Update documentation Jeff Kirsher
2010-12-11 6:17 ` [PATCH 07/27] MAINTAINERS: Update Intel Wired LAN info Jeff Kirsher
2010-12-11 6:17 ` [PATCH 08/27] e1000: fix return value not set on error Jeff Kirsher
2010-12-11 6:17 ` Jeff Kirsher
2010-12-11 6:17 ` [PATCH 09/27] Intel Wired LAN drivers: Use static const Jeff Kirsher
2010-12-11 6:17 ` [PATCH 10/27] ixgb: Don't check for vlan group on transmit Jeff Kirsher
2010-12-13 1:00 ` Jesse Gross
2010-12-13 18:43 ` Tantilov, Emil S
2010-12-14 3:40 ` Jesse Gross
2010-12-14 18:00 ` Tantilov, Emil S
2010-12-11 19:44 ` [net-next 00/27][pull-request] Intel Wired LAN Driver Updates David Miller
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=1292048241-22026-2-git-send-email-jeffrey.t.kirsher@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=bphilips@novell.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=netdev@vger.kernel.org \
/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).