Thread (16 messages) 16 messages, 3 authors, 2010-12-11

[net-next-2.6 03/27] Documentation/networking/igb.txt: update documentation

flat view
STALE5797d

From: Jeff Kirsher <hidden>
Date: 2010-12-10 09:51:20
Subsystem: documentation, networking [general], the rest · Maintainers: Jonathan Corbet, "David S. Miller", Eric Dumazet, Jakub Kicinski, Paolo Abeni, Linus Torvalds

Revision v1 of 2 in this series.

Revisions (2)
  1. v1 current
  2. v1
Update Intel Wired LAN igb documentation.

Signed-off-by: Jeff Kirsher <redacted>
---
 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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help