From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net
To: davem@davemleft.org
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
netdev@vger.kernel.org, gospo@redhat.com, bphilips@novell.com
Subject: [net-next-2.6 03/27] Documentation/networking/igb.txt: update documentation
Date: Fri, 10 Dec 2010 01:50:43 -0800 [thread overview]
Message-ID: <1291974667-30254-4-git-send-email-jeffrey.t.kirsher@intel.com> (raw)
In-Reply-To: <1291974667-30254-1-git-send-email-jeffrey.t.kirsher@intel.com>
Update Intel Wired LAN igb documentation.
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
---
Documentation/networking/igb.txt | 22 +++++++++++++++++++---
1 files changed, 19 insertions(+), 3 deletions(-)
diff --git a/Documentation/networking/igb.txt b/Documentation/networking/igb.txt
index ab2d718..393bdb7 100644
--- a/Documentation/networking/igb.txt
+++ b/Documentation/networking/igb.txt
@@ -36,6 +36,7 @@ Default Value: 0
This parameter adds support for SR-IOV. It causes the driver to spawn up to
max_vfs worth of virtual function.
+
Additional Configurations
=========================
@@ -60,7 +61,8 @@ Additional Configurations
Ethtool
-------
The driver utilizes the ethtool interface for driver configuration and
- diagnostics, as well as displaying statistical information.
+ diagnostics, as well as displaying statistical information. The latest
+ version of Ethtool can be found at:
http://sourceforge.net/projects/gkernel.
@@ -103,8 +105,8 @@ Additional Configurations
NOTE: You need to have inet_lro enabled via either the CONFIG_INET_LRO or
CONFIG_INET_LRO_MODULE kernel config option. Additionally, if
- CONFIG_INET_LRO_MODULE is used, the inet_lro module needs to be loaded
- before the igb driver.
+ CONFIG_INET_LRO_MODULE is used, the inet_lro module needs to be loaded before
+ the igb driver.
You can verify that the driver is using LRO by looking at these counters in
Ethtool:
@@ -116,6 +118,20 @@ Additional Configurations
NOTE: IPv6 and UDP are not supported by LRO.
+ MAC and VLAN anti-spoofing feature
+ ----------------------------------
+ When a malicious driver attempts to send a spoofed packet, it is dropped by
+ the hardware and not transmitted. An interrupt is sent to the PF driver
+ notifying it of the spoof attempt.
+
+ When a spoofed packet is detected the PF driver will send the following
+ message to the system log (displayed by the "dmesg" command):
+
+ Spoof event(s) detected on VF(n)
+
+ Where n=the VF that attempted to do the spoofing.
+
+
Support
=======
--
1.7.3.2
next prev parent reply other threads:[~2010-12-10 9:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 9:50 [net-next 00/27][pull-request] Intel Wired LAN Driver Updates Jeff Kirsher
2010-12-10 9:50 ` [net-next-2.6 01/27] Documentation/networking/e1000.txt: Update documentation Jeff Kirsher
2010-12-10 9:50 ` [net-next-2.6 02/27] Documentation/networking/e1000e.txt: " Jeff Kirsher
2010-12-10 9:50 ` Jeff Kirsher [this message]
2010-12-10 15:50 ` [net-next-2.6 03/27] Documentation/networking/igb.txt: update documentation Ben Hutchings
2010-12-10 20:21 ` David Miller
2010-12-11 5:26 ` Jeff Kirsher
2010-12-11 5:25 ` Jeff Kirsher
2010-12-10 9:50 ` [net-next-2.6 04/27] Documentation/networking/igbvf.txt: Update documentation Jeff Kirsher
2010-12-10 9:50 ` [net-next-2.6 05/27] Documentation/networking/ixgbe.txt: Update ixgbe documentation Jeff Kirsher
2010-12-10 9:50 ` [net-next-2.6 06/27] Documentation/networking/ixgbevf.txt: Update documentation Jeff Kirsher
2010-12-10 9:50 ` [net-next-2.6 07/27] MAINTAINERS: Update Intel Wired LAN info Jeff Kirsher
2010-12-10 9:50 ` [net-next-2.6 08/27] e1000: fix return value not set on error Jeff Kirsher
2010-12-10 9:50 ` Jeff Kirsher
2010-12-10 9:50 ` [net-next-2.6 09/27] Intel Wired LAN drivers: Use static const Jeff Kirsher
2010-12-10 9:50 ` [net-next-2.6 10/27] ixgb: Don't check for vlan group on transmit Jeff Kirsher
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=1291974667-30254-4-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).