Merge branch 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel...
[GitHub/mt8127/android_kernel_alcatel_ttab.git] / Documentation / networking / igb.txt
CommitLineData
b55c52b1
JK
1Linux* Base Driver for Intel(R) Network Connection
2==================================================
3
4Intel Gigabit Linux driver.
5Copyright(c) 1999 - 2010 Intel Corporation.
6
7Contents
8========
9
10- Identifying Your Adapter
11- Additional Configurations
12- Support
13
14Identifying Your Adapter
15========================
16
17This driver supports all 82575, 82576 and 82580-based Intel (R) gigabit network
18connections.
19
20For specific information on how to identify your adapter, go to the Adapter &
21Driver ID Guide at:
22
23 http://support.intel.com/support/go/network/adapter/idguide.htm
24
25Command Line Parameters
26=======================
27
28The default value for each parameter is generally the recommended setting,
29unless otherwise noted.
30
31max_vfs
32-------
33Valid Range: 0-7
34Default Value: 0
35
36This parameter adds support for SR-IOV. It causes the driver to spawn up to
37max_vfs worth of virtual function.
38
1ffd7246 39
b55c52b1
JK
40Additional Configurations
41=========================
42
43 Jumbo Frames
44 ------------
45 Jumbo Frames support is enabled by changing the MTU to a value larger than
46 the default of 1500. Use the ifconfig command to increase the MTU size.
47 For example:
48
49 ifconfig eth<x> mtu 9000 up
50
51 This setting is not saved across reboots.
52
53 Notes:
54
55 - The maximum MTU setting for Jumbo Frames is 9216. This value coincides
56 with the maximum Jumbo Frames size of 9234 bytes.
57
58 - Using Jumbo Frames at 10 or 100 Mbps may result in poor performance or
59 loss of link.
60
61 Ethtool
62 -------
63 The driver utilizes the ethtool interface for driver configuration and
1ffd7246 64 diagnostics, as well as displaying statistical information. The latest
68f20d94 65 version of ethtool can be found at:
b55c52b1 66
1ffd7246 67 http://ftp.kernel.org/pub/software/network/ethtool/
b55c52b1
JK
68
69 Enabling Wake on LAN* (WoL)
70 ---------------------------
68f20d94 71 WoL is configured through the ethtool* utility.
b55c52b1 72
68f20d94 73 For instructions on enabling WoL with ethtool, refer to the ethtool man page.
b55c52b1
JK
74
75 WoL will be enabled on the system during the next shut down or reboot.
76 For this driver version, in order to enable WoL, the igb driver must be
77 loaded when shutting down or rebooting the system.
78
79 Wake On LAN is only supported on port A of multi-port adapters.
80
81 Wake On LAN is not supported for the Intel(R) Gigabit VT Quad Port Server
82 Adapter.
83
84 Multiqueue
85 ----------
86 In this mode, a separate MSI-X vector is allocated for each queue and one
87 for "other" interrupts such as link status change and errors. All
88 interrupts are throttled via interrupt moderation. Interrupt moderation
89 must be used to avoid interrupt storms while the driver is processing one
90 interrupt. The moderation value should be at least as large as the expected
91 time for the driver to process an interrupt. Multiqueue is off by default.
92
93 REQUIREMENTS: MSI-X support is required for Multiqueue. If MSI-X is not
94 found, the system will fallback to MSI or to Legacy interrupts.
95
7c158399
GR
96 MAC and VLAN anti-spoofing feature
97 ----------------------------------
98 When a malicious driver attempts to send a spoofed packet, it is dropped by
99 the hardware and not transmitted. An interrupt is sent to the PF driver
100 notifying it of the spoof attempt.
101
102 When a spoofed packet is detected the PF driver will send the following
103 message to the system log (displayed by the "dmesg" command):
104
105 Spoof event(s) detected on VF(n)
106
107 Where n=the VF that attempted to do the spoofing.
108
b55c52b1
JK
109Support
110=======
111
112For general information, go to the Intel support website at:
113
114 www.intel.com/support/
115
116or the Intel Wired Networking project hosted by Sourceforge at:
117
118 http://sourceforge.net/projects/e1000
119
120If an issue is identified with the released source code on the supported
121kernel with a supported adapter, email the specific information related
122to the issue to e1000-devel@lists.sf.net