Blame view
Documentation/networking/e1000.txt
24.9 KB
1da177e4c Linux-2.6.12-rc2 |
1 2 |
Linux* Base Driver for the Intel(R) PRO/1000 Family of Adapters =============================================================== |
de3edab42 e1000: update REA... |
3 |
September 26, 2006 |
1da177e4c Linux-2.6.12-rc2 |
4 5 6 7 8 9 10 |
Contents ======== - In This Release - Identifying Your Adapter |
de3edab42 e1000: update REA... |
11 |
- Building and Installation |
1da177e4c Linux-2.6.12-rc2 |
12 13 14 15 16 17 18 19 20 21 22 |
- Command Line Parameters - Speed and Duplex Configuration - Additional Configurations - Known Issues - Support In This Release =============== This file describes the Linux* Base Driver for the Intel(R) PRO/1000 Family |
55be062d2 e1000: update the... |
23 |
of Adapters. This driver includes support for Itanium(R)2-based systems. |
1da177e4c Linux-2.6.12-rc2 |
24 |
|
55be062d2 e1000: update the... |
25 26 |
For questions related to hardware requirements, refer to the documentation supplied with your Intel PRO/1000 adapter. All hardware requirements listed |
1da177e4c Linux-2.6.12-rc2 |
27 |
apply to use with Linux. |
55be062d2 e1000: update the... |
28 29 30 31 32 33 34 35 36 37 38 39 40 41 |
The following features are now available in supported kernels: - Native VLANs - Channel Bonding (teaming) - SNMP Channel Bonding documentation can be found in the Linux kernel source: /Documentation/networking/bonding.txt The driver information previously displayed in the /proc filesystem is not supported in this release. Alternatively, you can use ethtool (version 1.6 or later), lspci, and ifconfig to obtain the same information. Instructions on updating ethtool can be found in the section "Additional Configurations" later in this document. |
de3edab42 e1000: update REA... |
42 43 |
NOTE: The Intel(R) 82562v 10/100 Network Connection only provides 10/100 support. |
1da177e4c Linux-2.6.12-rc2 |
44 45 46 |
Identifying Your Adapter ======================== |
55be062d2 e1000: update the... |
47 |
For more information on how to identify your adapter, go to the Adapter & |
1da177e4c Linux-2.6.12-rc2 |
48 49 50 |
Driver ID Guide at: http://support.intel.com/support/network/adapter/pro100/21397.htm |
55be062d2 e1000: update the... |
51 |
For the latest Intel network drivers for Linux, refer to the following |
de3edab42 e1000: update REA... |
52 |
website. In the search field, enter your adapter name or type, or use the |
1da177e4c Linux-2.6.12-rc2 |
53 54 55 |
networking link on the left to search for your adapter: http://downloadfinder.intel.com/scripts-df/support_intel.asp |
1da177e4c Linux-2.6.12-rc2 |
56 |
|
de3edab42 e1000: update REA... |
57 58 |
Command Line Parameters ======================= |
55be062d2 e1000: update the... |
59 60 |
If the driver is built as a module, the following optional parameters |
de3edab42 e1000: update REA... |
61 62 |
are used by entering them on the command line with the modprobe command using this syntax: |
1da177e4c Linux-2.6.12-rc2 |
63 64 |
modprobe e1000 [<option>=<VAL1>,<VAL2>,...] |
1da177e4c Linux-2.6.12-rc2 |
65 |
For example, with two PRO/1000 PCI adapters, entering: |
de3edab42 e1000: update REA... |
66 |
modprobe e1000 TxDescriptors=80,128 |
1da177e4c Linux-2.6.12-rc2 |
67 |
|
de3edab42 e1000: update REA... |
68 69 |
loads the e1000 driver with 80 TX descriptors for the first adapter and 128 TX descriptors for the second adapter. |
1da177e4c Linux-2.6.12-rc2 |
70 71 |
The default value for each parameter is generally the recommended setting, |
55be062d2 e1000: update the... |
72 73 74 75 76 |
unless otherwise noted. NOTES: For more information about the AutoNeg, Duplex, and Speed parameters, see the "Speed and Duplex Configuration" section in this document. |
1da177e4c Linux-2.6.12-rc2 |
77 |
|
55be062d2 e1000: update the... |
78 79 80 81 |
For more information about the InterruptThrottleRate, RxIntDelay, TxIntDelay, RxAbsIntDelay, and TxAbsIntDelay parameters, see the application note at: http://www.intel.com/design/network/applnots/ap450.htm |
1da177e4c Linux-2.6.12-rc2 |
82 |
|
55be062d2 e1000: update the... |
83 |
A descriptor describes a data buffer and attributes related to |
de3edab42 e1000: update REA... |
84 |
the data buffer. This information is accessed by the hardware. |
1da177e4c Linux-2.6.12-rc2 |
85 |
|
1da177e4c Linux-2.6.12-rc2 |
86 |
|
55be062d2 e1000: update the... |
87 88 89 90 |
AutoNeg ------- (Supported only on adapters with copper connections) Valid Range: 0x01-0x0F, 0x20-0x2F |
1da177e4c Linux-2.6.12-rc2 |
91 |
Default Value: 0x2F |
55be062d2 e1000: update the... |
92 |
|
de3edab42 e1000: update REA... |
93 94 95 |
This parameter is a bit-mask that specifies the speed and duplex settings advertised by the adapter. When this parameter is used, the Speed and Duplex parameters must not be specified. |
55be062d2 e1000: update the... |
96 97 98 99 100 101 102 103 104 |
NOTE: Refer to the Speed and Duplex section of this readme for more information on the AutoNeg parameter. Duplex ------ (Supported only on adapters with copper connections) Valid Range: 0-2 (0=auto-negotiate, 1=half, 2=full) |
1da177e4c Linux-2.6.12-rc2 |
105 |
Default Value: 0 |
55be062d2 e1000: update the... |
106 |
|
de3edab42 e1000: update REA... |
107 108 109 110 111 |
This defines the direction in which data is allowed to flow. Can be either one or two-directional. If both Duplex and the link partner are set to auto-negotiate, the board auto-detects the correct duplex. If the link partner is forced (either full or half), Duplex defaults to half- duplex. |
55be062d2 e1000: update the... |
112 |
|
1da177e4c Linux-2.6.12-rc2 |
113 114 |
FlowControl |
de3edab42 e1000: update REA... |
115 |
----------- |
55be062d2 e1000: update the... |
116 117 118 119 120 |
Valid Range: 0-3 (0=none, 1=Rx only, 2=Tx only, 3=Rx&Tx) Default Value: Reads flow control settings from the EEPROM This parameter controls the automatic generation(Tx) and response(Rx) to Ethernet PAUSE frames. |
1da177e4c Linux-2.6.12-rc2 |
121 122 |
InterruptThrottleRate |
55be062d2 e1000: update the... |
123 |
--------------------- |
de3edab42 e1000: update REA... |
124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 |
(not supported on Intel(R) 82542, 82543 or 82544-based adapters) Valid Range: 0,1,3,100-100000 (0=off, 1=dynamic, 3=dynamic conservative) Default Value: 3 The driver can limit the amount of interrupts per second that the adapter will generate for incoming packets. It does this by writing a value to the adapter that is based on the maximum amount of interrupts that the adapter will generate per second. Setting InterruptThrottleRate to a value greater or equal to 100 will program the adapter to send out a maximum of that many interrupts per second, even if more packets have come in. This reduces interrupt load on the system and can lower CPU utilization under heavy load, but will increase latency as packets are not processed as quickly. The default behaviour of the driver previously assumed a static InterruptThrottleRate value of 8000, providing a good fallback value for all traffic types,but lacking in small packet performance and latency. The hardware can handle many more small packets per second however, and for this reason an adaptive interrupt moderation algorithm was implemented. Since 7.3.x, the driver has two adaptive modes (setting 1 or 3) in which it dynamically adjusts the InterruptThrottleRate value based on the traffic that it receives. After determining the type of incoming traffic in the last timeframe, it will adjust the InterruptThrottleRate to an appropriate value for that traffic. The algorithm classifies the incoming traffic every interval into classes. Once the class is determined, the InterruptThrottleRate value is adjusted to suit that traffic type the best. There are three classes defined: "Bulk traffic", for large amounts of packets of normal size; "Low latency", for small amounts of traffic and/or a significant percentage of small packets; and "Lowest latency", for almost completely small packets or minimal traffic. In dynamic conservative mode, the InterruptThrottleRate value is set to 4000 for traffic that falls in class "Bulk traffic". If traffic falls in the "Low latency" or "Lowest latency" class, the InterruptThrottleRate is increased stepwise to 20000. This default mode is suitable for most applications. For situations where low latency is vital such as cluster or grid computing, the algorithm can reduce latency even more when 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". Setting InterruptThrottleRate to 0 turns off any interrupt moderation and may improve small packet latency, but is generally not suitable for bulk throughput traffic. |
55be062d2 e1000: update the... |
173 174 |
NOTE: InterruptThrottleRate takes precedence over the TxAbsIntDelay and |
de3edab42 e1000: update REA... |
175 |
RxAbsIntDelay parameters. In other words, minimizing the receive |
55be062d2 e1000: update the... |
176 177 178 |
and/or transmit absolute delays does not force the controller to generate more interrupts than what the Interrupt Throttle Rate allows. |
de3edab42 e1000: update REA... |
179 |
CAUTION: If you are using the Intel(R) PRO/1000 CT Network Connection |
55be062d2 e1000: update the... |
180 181 |
(controller 82547), setting InterruptThrottleRate to a value greater than 75,000, may hang (stop transmitting) adapters |
de3edab42 e1000: update REA... |
182 183 |
under certain network conditions. If this occurs a NETDEV WATCHDOG message is logged in the system event log. In |
55be062d2 e1000: update the... |
184 |
addition, the controller is automatically reset, restoring |
de3edab42 e1000: update REA... |
185 |
the network connection. To eliminate the potential for the |
55be062d2 e1000: update the... |
186 187 188 189 190 |
hang, ensure that InterruptThrottleRate is set no greater than 75,000 and is not set to 0. NOTE: When e1000 is loaded with default settings and multiple adapters are in use simultaneously, the CPU utilization may increase non- |
de3edab42 e1000: update REA... |
191 |
linearly. In order to limit the CPU utilization without impacting |
55be062d2 e1000: update the... |
192 193 |
the overall throughput, we recommend that you load the driver as follows: |
de3edab42 e1000: update REA... |
194 |
modprobe e1000 InterruptThrottleRate=3000,3000,3000 |
55be062d2 e1000: update the... |
195 196 |
This sets the InterruptThrottleRate to 3000 interrupts/sec for |
de3edab42 e1000: update REA... |
197 |
the first, second, and third instances of the driver. The range |
55be062d2 e1000: update the... |
198 199 |
of 2000 to 3000 interrupts per second works on a majority of systems and is a good starting point, but the optimal value will |
de3edab42 e1000: update REA... |
200 |
be platform-specific. If CPU utilization is not a concern, use |
55be062d2 e1000: update the... |
201 |
RX_POLLING (NAPI) and default driver settings. |
1da177e4c Linux-2.6.12-rc2 |
202 |
|
de3edab42 e1000: update REA... |
203 |
|
1da177e4c Linux-2.6.12-rc2 |
204 |
RxDescriptors |
55be062d2 e1000: update the... |
205 206 207 |
------------- Valid Range: 80-256 for 82542 and 82543-based adapters 80-4096 for all other supported adapters |
1da177e4c Linux-2.6.12-rc2 |
208 |
Default Value: 256 |
1da177e4c Linux-2.6.12-rc2 |
209 |
|
de3edab42 e1000: update REA... |
210 211 212 213 214 215 216 217 218 219 220 221 |
This value specifies the number of receive buffer descriptors allocated by the driver. Increasing this value allows the driver to buffer more incoming packets, at the expense of increased system memory utilization. Each descriptor is 16 bytes. A receive buffer is also allocated for each descriptor and can be either 2048, 4096, 8192, or 16384 bytes, depending on the MTU setting. The maximum MTU size is 16110. NOTE: MTU designates the frame size. It only needs to be set for Jumbo Frames. Depending on the available system resources, the request for a higher number of receive descriptors may be denied. In this case, use a lower number. |
1da177e4c Linux-2.6.12-rc2 |
222 |
|
1da177e4c Linux-2.6.12-rc2 |
223 224 |
RxIntDelay |
55be062d2 e1000: update the... |
225 226 |
---------- Valid Range: 0-65535 (0=off) |
1da177e4c Linux-2.6.12-rc2 |
227 |
Default Value: 0 |
55be062d2 e1000: update the... |
228 229 230 |
This value delays the generation of receive interrupts in units of 1.024 microseconds. Receive interrupt reduction can improve CPU efficiency if |
de3edab42 e1000: update REA... |
231 |
properly tuned for specific network traffic. Increasing this value adds |
55be062d2 e1000: update the... |
232 |
extra latency to frame reception and can end up decreasing the throughput |
de3edab42 e1000: update REA... |
233 |
of TCP traffic. If the system is reporting dropped receives, this value |
55be062d2 e1000: update the... |
234 235 236 237 |
may be set too high, causing the driver to run out of available receive descriptors. CAUTION: When setting RxIntDelay to a value other than 0, adapters may |
de3edab42 e1000: update REA... |
238 |
hang (stop transmitting) under certain network conditions. If |
55be062d2 e1000: update the... |
239 |
this occurs a NETDEV WATCHDOG message is logged in the system |
de3edab42 e1000: update REA... |
240 241 |
event log. In addition, the controller is automatically reset, restoring the network connection. To eliminate the potential |
55be062d2 e1000: update the... |
242 243 244 245 246 247 248 |
for the hang ensure that RxIntDelay is set to 0. RxAbsIntDelay ------------- (This parameter is supported only on 82540, 82545 and later adapters.) Valid Range: 0-65535 (0=off) |
1da177e4c Linux-2.6.12-rc2 |
249 |
Default Value: 128 |
55be062d2 e1000: update the... |
250 251 |
This value, in units of 1.024 microseconds, limits the delay in which a |
de3edab42 e1000: update REA... |
252 |
receive interrupt is generated. Useful only if RxIntDelay is non-zero, |
55be062d2 e1000: update the... |
253 254 255 256 257 258 259 260 261 |
this value ensures that an interrupt is generated after the initial packet is received within the set amount of time. Proper tuning, along with RxIntDelay, may improve traffic throughput in specific network conditions. Speed ----- (This parameter is supported only on adapters with copper connections.) |
1da177e4c Linux-2.6.12-rc2 |
262 |
Valid Settings: 0, 10, 100, 1000 |
55be062d2 e1000: update the... |
263 264 265 |
Default Value: 0 (auto-negotiate at all supported speeds) Speed forces the line speed to the specified value in megabits per second |
de3edab42 e1000: update REA... |
266 |
(Mbps). If this parameter is not specified or is set to 0 and the link |
55be062d2 e1000: update the... |
267 |
partner is set to auto-negotiate, the board will auto-detect the correct |
de3edab42 e1000: update REA... |
268 |
speed. Duplex should also be set when Speed is set to either 10 or 100. |
55be062d2 e1000: update the... |
269 |
|
1da177e4c Linux-2.6.12-rc2 |
270 271 |
TxDescriptors |
55be062d2 e1000: update the... |
272 273 274 |
------------- Valid Range: 80-256 for 82542 and 82543-based adapters 80-4096 for all other supported adapters |
1da177e4c Linux-2.6.12-rc2 |
275 |
Default Value: 256 |
1da177e4c Linux-2.6.12-rc2 |
276 |
|
55be062d2 e1000: update the... |
277 |
This value is the number of transmit descriptors allocated by the driver. |
de3edab42 e1000: update REA... |
278 |
Increasing this value allows the driver to queue more transmits. Each |
55be062d2 e1000: update the... |
279 280 281 282 283 |
descriptor is 16 bytes. NOTE: Depending on the available system resources, the request for a higher number of transmit descriptors may be denied. In this case, use a lower number. |
1da177e4c Linux-2.6.12-rc2 |
284 285 |
TxIntDelay |
55be062d2 e1000: update the... |
286 287 |
---------- Valid Range: 0-65535 (0=off) |
1da177e4c Linux-2.6.12-rc2 |
288 |
Default Value: 64 |
55be062d2 e1000: update the... |
289 290 |
This value delays the generation of transmit interrupts in units of |
de3edab42 e1000: update REA... |
291 292 |
1.024 microseconds. Transmit interrupt reduction can improve CPU efficiency if properly tuned for specific network traffic. If the |
55be062d2 e1000: update the... |
293 294 295 296 297 298 299 300 |
system is reporting dropped transmits, this value may be set too high causing the driver to run out of available transmit descriptors. TxAbsIntDelay ------------- (This parameter is supported only on 82540, 82545 and later adapters.) Valid Range: 0-65535 (0=off) |
1da177e4c Linux-2.6.12-rc2 |
301 |
Default Value: 64 |
55be062d2 e1000: update the... |
302 303 |
This value, in units of 1.024 microseconds, limits the delay in which a |
de3edab42 e1000: update REA... |
304 |
transmit interrupt is generated. Useful only if TxIntDelay is non-zero, |
55be062d2 e1000: update the... |
305 306 307 308 309 310 311 312 313 |
this value ensures that an interrupt is generated after the initial packet is sent on the wire within the set amount of time. Proper tuning, along with TxIntDelay, may improve traffic throughput in specific network conditions. XsumRX ------ (This parameter is NOT supported on the 82542-based adapter.) Valid Range: 0-1 |
1da177e4c Linux-2.6.12-rc2 |
314 |
Default Value: 1 |
55be062d2 e1000: update the... |
315 316 317 |
A value of '1' indicates that the driver should enable IP checksum offload for received packets (both UDP and TCP) to the adapter hardware. |
1da177e4c Linux-2.6.12-rc2 |
318 319 320 |
Speed and Duplex Configuration ============================== |
55be062d2 e1000: update the... |
321 322 |
Three keywords are used to control the speed and duplex configuration. These keywords are Speed, Duplex, and AutoNeg. |
1da177e4c Linux-2.6.12-rc2 |
323 |
|
55be062d2 e1000: update the... |
324 |
If the board uses a fiber interface, these keywords are ignored, and the |
1da177e4c Linux-2.6.12-rc2 |
325 326 327 |
fiber interface board only links at 1000 Mbps full-duplex. For copper-based boards, the keywords interact as follows: |
de3edab42 e1000: update REA... |
328 |
The default operation is auto-negotiate. The board advertises all |
55be062d2 e1000: update the... |
329 330 |
supported speed and duplex combinations, and it links at the highest common speed and duplex mode IF the link partner is set to auto-negotiate. |
1da177e4c Linux-2.6.12-rc2 |
331 |
|
55be062d2 e1000: update the... |
332 333 |
If Speed = 1000, limited auto-negotiation is enabled and only 1000 Mbps is advertised (The 1000BaseT spec requires auto-negotiation.) |
1da177e4c Linux-2.6.12-rc2 |
334 |
|
de3edab42 e1000: update REA... |
335 336 |
If Speed = 10 or 100, then both Speed and Duplex should be set. Auto- negotiation is disabled, and the AutoNeg parameter is ignored. Partner |
55be062d2 e1000: update the... |
337 338 339 340 341 342 |
SHOULD also be forced. The AutoNeg parameter is used when more control is required over the auto-negotiation process. It should be used when you wish to control which speed and duplex combinations are advertised during the auto-negotiation process. |
de3edab42 e1000: update REA... |
343 |
The parameter may be specified as either a decimal or hexadecimal value as |
55be062d2 e1000: update the... |
344 |
determined by the bitmap below. |
1da177e4c Linux-2.6.12-rc2 |
345 |
|
55be062d2 e1000: update the... |
346 347 348 349 350 |
Bit position 7 6 5 4 3 2 1 0 Decimal Value 128 64 32 16 8 4 2 1 Hex value 80 40 20 10 8 4 2 1 Speed (Mbps) N/A N/A 1000 N/A 100 100 10 10 Duplex Full Full Half Full Half |
1da177e4c Linux-2.6.12-rc2 |
351 |
|
55be062d2 e1000: update the... |
352 |
Some examples of using AutoNeg: |
1da177e4c Linux-2.6.12-rc2 |
353 |
|
55be062d2 e1000: update the... |
354 355 356 357 358 359 360 361 362 |
modprobe e1000 AutoNeg=0x01 (Restricts autonegotiation to 10 Half) modprobe e1000 AutoNeg=1 (Same as above) modprobe e1000 AutoNeg=0x02 (Restricts autonegotiation to 10 Full) modprobe e1000 AutoNeg=0x03 (Restricts autonegotiation to 10 Half or 10 Full) modprobe e1000 AutoNeg=0x04 (Restricts autonegotiation to 100 Half) modprobe e1000 AutoNeg=0x05 (Restricts autonegotiation to 10 Half or 100 Half) modprobe e1000 AutoNeg=0x020 (Restricts autonegotiation to 1000 Full) modprobe e1000 AutoNeg=32 (Same as above) |
1da177e4c Linux-2.6.12-rc2 |
363 |
|
55be062d2 e1000: update the... |
364 365 366 367 368 |
Note that when this parameter is used, Speed and Duplex must not be specified. If the link partner is forced to a specific speed and duplex, then this parameter should not be used. Instead, use the Speed and Duplex parameters previously mentioned to force the adapter to the same speed and duplex. |
1da177e4c Linux-2.6.12-rc2 |
369 370 371 372 373 374 375 |
Additional Configurations ========================= Configuring the Driver on Different Distributions ------------------------------------------------- |
55be062d2 e1000: update the... |
376 |
Configuring a network driver to load properly when the system is started |
de3edab42 e1000: update REA... |
377 |
is distribution dependent. Typically, the configuration process involves |
55be062d2 e1000: update the... |
378 |
adding an alias line to /etc/modules.conf or /etc/modprobe.conf as well |
de3edab42 e1000: update REA... |
379 |
as editing other system startup scripts and/or configuration files. Many |
55be062d2 e1000: update the... |
380 381 |
popular Linux distributions ship with tools to make these changes for you. To learn the proper way to configure a network device for your system, |
de3edab42 e1000: update REA... |
382 |
refer to your distribution documentation. If during this process you are |
55be062d2 e1000: update the... |
383 |
asked for the driver or module name, the name for the Linux Base Driver |
de3edab42 e1000: update REA... |
384 |
for the Intel(R) PRO/1000 Family of Adapters is e1000. |
1da177e4c Linux-2.6.12-rc2 |
385 |
|
55be062d2 e1000: update the... |
386 387 |
As an example, if you install the e1000 driver for two PRO/1000 adapters (eth0 and eth1) and set the speed and duplex to 10full and 100half, add |
de3edab42 e1000: update REA... |
388 |
the following to modules.conf or or modprobe.conf: |
1da177e4c Linux-2.6.12-rc2 |
389 390 391 392 393 394 395 |
alias eth0 e1000 alias eth1 e1000 options e1000 Speed=10,100 Duplex=2,1 Viewing Link Messages --------------------- |
55be062d2 e1000: update the... |
396 |
Link messages will not be displayed to the console if the distribution is |
de3edab42 e1000: update REA... |
397 |
restricting system messages. In order to see network driver link messages |
55be062d2 e1000: update the... |
398 |
on your console, set dmesg to eight by entering the following: |
1da177e4c Linux-2.6.12-rc2 |
399 400 401 402 403 404 405 |
dmesg -n 8 NOTE: This setting is not saved across reboots. Jumbo Frames ------------ |
de3edab42 e1000: update REA... |
406 407 408 |
Jumbo Frames support is enabled by changing the MTU to a value larger than the default of 1500. Use the ifconfig command to increase the MTU size. For example: |
55be062d2 e1000: update the... |
409 410 411 412 413 414 415 |
ifconfig eth<x> mtu 9000 up This setting is not saved across reboots. It can be made permanent if you add: MTU=9000 |
1da177e4c Linux-2.6.12-rc2 |
416 |
|
55be062d2 e1000: update the... |
417 418 419 |
to the file /etc/sysconfig/network-scripts/ifcfg-eth<x>. This example applies to the Red Hat distributions; other distributions may store this setting in a different location. |
1da177e4c Linux-2.6.12-rc2 |
420 |
|
55be062d2 e1000: update the... |
421 |
Notes: |
1da177e4c Linux-2.6.12-rc2 |
422 |
|
55be062d2 e1000: update the... |
423 424 |
- To enable Jumbo Frames, increase the MTU size on the interface beyond 1500. |
de3edab42 e1000: update REA... |
425 426 |
- The maximum MTU setting for Jumbo Frames is 16110. This value coincides |
55be062d2 e1000: update the... |
427 |
with the maximum Jumbo Frames size of 16128. |
de3edab42 e1000: update REA... |
428 |
|
55be062d2 e1000: update the... |
429 430 |
- Using Jumbo Frames at 10 or 100 Mbps may result in poor performance or loss of link. |
de3edab42 e1000: update REA... |
431 |
|
55be062d2 e1000: update the... |
432 433 |
- Some Intel gigabit adapters that support Jumbo Frames have a frame size limit of 9238 bytes, with a corresponding MTU size limit of 9216 bytes. |
de3edab42 e1000: update REA... |
434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 |
The adapters with this limitation are based on the Intel(R) 82571EB, 82572EI, 82573L and 80003ES2LAN controller. These correspond to the following product names: Intel(R) PRO/1000 PT Server Adapter Intel(R) PRO/1000 PT Desktop Adapter Intel(R) PRO/1000 PT Network Connection Intel(R) PRO/1000 PT Dual Port Server Adapter Intel(R) PRO/1000 PT Dual Port Network Connection Intel(R) PRO/1000 PF Server Adapter Intel(R) PRO/1000 PF Network Connection Intel(R) PRO/1000 PF Dual Port Server Adapter Intel(R) PRO/1000 PB Server Connection Intel(R) PRO/1000 PL Network Connection Intel(R) PRO/1000 EB Network Connection with I/O Acceleration Intel(R) PRO/1000 EB Backplane Connection with I/O Acceleration Intel(R) PRO/1000 PT Quad Port Server Adapter - Adapters based on the Intel(R) 82542 and 82573V/E controller do not support Jumbo Frames. These correspond to the following product names: Intel(R) PRO/1000 Gigabit Server Adapter Intel(R) PRO/1000 PM Network Connection - The following adapters do not support Jumbo Frames: Intel(R) 82562V 10/100 Network Connection Intel(R) 82566DM Gigabit Network Connection Intel(R) 82566DC Gigabit Network Connection Intel(R) 82566MM Gigabit Network Connection Intel(R) 82566MC Gigabit Network Connection Intel(R) 82562GT 10/100 Network Connection Intel(R) 82562G 10/100 Network Connection |
1da177e4c Linux-2.6.12-rc2 |
464 |
|
1da177e4c Linux-2.6.12-rc2 |
465 466 467 |
Ethtool ------- |
1da177e4c Linux-2.6.12-rc2 |
468 469 470 471 472 |
The driver utilizes the ethtool interface for driver configuration and diagnostics, as well as displaying statistical information. Ethtool version 1.6 or later is required for this functionality. The latest release of ethtool can be found from |
55be062d2 e1000: update the... |
473 |
http://sourceforge.net/projects/gkernel. |
1da177e4c Linux-2.6.12-rc2 |
474 |
|
de3edab42 e1000: update REA... |
475 |
NOTE: Ethtool 1.6 only supports a limited set of ethtool options. Support |
55be062d2 e1000: update the... |
476 477 |
for a more complete ethtool feature set can be enabled by upgrading ethtool to ethtool-1.8.1. |
1da177e4c Linux-2.6.12-rc2 |
478 479 480 |
Enabling Wake on LAN* (WoL) --------------------------- |
de3edab42 e1000: update REA... |
481 482 |
WoL is configured through the Ethtool* utility. Ethtool is included with all versions of Red Hat after Red Hat 7.2. For other Linux distributions, |
55be062d2 e1000: update the... |
483 |
download and install Ethtool from the following website: |
1da177e4c Linux-2.6.12-rc2 |
484 |
http://sourceforge.net/projects/gkernel. |
55be062d2 e1000: update the... |
485 |
For instructions on enabling WoL with Ethtool, refer to the website listed |
1da177e4c Linux-2.6.12-rc2 |
486 |
above. |
55be062d2 e1000: update the... |
487 488 |
WoL will be enabled on the system during the next shut down or reboot. For this driver version, in order to enable WoL, the e1000 driver must be |
1da177e4c Linux-2.6.12-rc2 |
489 |
loaded when shutting down or rebooting the system. |
de3edab42 e1000: update REA... |
490 491 492 493 494 |
Wake On LAN is only supported on port A for the following devices: Intel(R) PRO/1000 PT Dual Port Network Connection Intel(R) PRO/1000 PT Dual Port Server Connection Intel(R) PRO/1000 PT Dual Port Server Adapter Intel(R) PRO/1000 PF Dual Port Server Adapter |
c3570acb5 e1000: delete non... |
495 |
Intel(R) PRO/1000 PT Quad Port Server Adapter |
de3edab42 e1000: update REA... |
496 |
|
1da177e4c Linux-2.6.12-rc2 |
497 498 |
NAPI ---- |
c3570acb5 e1000: delete non... |
499 |
NAPI (Rx polling mode) is enabled in the e1000 driver. |
1da177e4c Linux-2.6.12-rc2 |
500 501 502 503 504 505 |
See www.cyberus.ca/~hadi/usenix-paper.tgz for more information on NAPI. Known Issues ============ |
de3edab42 e1000: update REA... |
506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 |
Dropped Receive Packets on Half-duplex 10/100 Networks ------------------------------------------------------ If you have an Intel PCI Express adapter running at 10mbps or 100mbps, half- duplex, you may observe occasional dropped receive packets. There are no workarounds for this problem in this network configuration. The network must be updated to operate in full-duplex, and/or 1000mbps only. Jumbo Frames System Requirement ------------------------------- Memory allocation failures have been observed on Linux systems with 64 MB of RAM or less that are running Jumbo Frames. If you are using Jumbo Frames, your system may require more than the advertised minimum requirement of 64 MB of system memory. Performance Degradation with Jumbo Frames ----------------------------------------- Degradation in throughput performance may be observed in some Jumbo frames environments. If this is observed, increasing the application's socket buffer size and/or increasing the /proc/sys/net/ipv4/tcp_*mem entry values may help. See the specific application manual and /usr/src/linux*/Documentation/ networking/ip-sysctl.txt for more details. Jumbo Frames on Foundry BigIron 8000 switch ------------------------------------------- There is a known issue using Jumbo frames when connected to a Foundry BigIron 8000 switch. This is a 3rd party limitation. If you experience loss of packets, lower the MTU size. Allocating Rx Buffers when Using Jumbo Frames --------------------------------------------- Allocating Rx buffers when using Jumbo Frames on 2.6.x kernels may fail if the available memory is heavily fragmented. This issue may be seen with PCI-X adapters or with packet split disabled. This can be reduced or eliminated by changing the amount of available memory for receive buffer allocation, by increasing /proc/sys/vm/min_free_kbytes. Multiple Interfaces on Same Ethernet Broadcast Network ------------------------------------------------------ Due to the default ARP behavior on Linux, it is not possible to have one system on two IP networks in the same Ethernet broadcast domain (non-partitioned switch) behave as expected. All Ethernet interfaces will respond to IP traffic for any IP address assigned to the system. This results in unbalanced receive traffic. If you have multiple interfaces in a server, either turn on ARP filtering by entering: echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter (this only works if your kernel's version is higher than 2.4.5), NOTE: This setting is not saved across reboots. The configuration change can be made permanent by adding the line: net.ipv4.conf.all.arp_filter = 1 to the file /etc/sysctl.conf or, install the interfaces in separate broadcast domains (either in different switches or in a switch partitioned to VLANs). 82541/82547 can't link or are slow to link with some link partners ----------------------------------------------------------------- There is a known compatibility issue with 82541/82547 and some low-end switches where the link will not be established, or will be slow to establish. In particular, these switches are known to be incompatible with 82541/82547: Planex FXG-08TE I-O Data ETG-SH8 To workaround this issue, the driver can be compiled with an override of the PHY's master/slave setting. Forcing master or forcing slave mode will improve time-to-link. # make CFLAGS_EXTRA=-DE1000_MASTER_SLAVE=<n> Where <n> is: 0 = Hardware default 1 = Master mode 2 = Slave mode 3 = Auto master/slave Disable rx flow control with ethtool ------------------------------------ In order to disable receive flow control using ethtool, you must turn off auto-negotiation on the same command line. For example: ethtool -A eth? autoneg off rx off Unplugging network cable while ethtool -p is running ---------------------------------------------------- In kernel versions 2.5.50 and later (including 2.6 kernel), unplugging the network cable while ethtool -p is running will cause the system to become unresponsive to keyboard commands, except for control-alt-delete. Restarting the system appears to be the only remedy. |
1da177e4c Linux-2.6.12-rc2 |
605 606 607 608 609 610 611 612 |
Support ======= For general information, go to the Intel support website at: http://support.intel.com |
de3edab42 e1000: update REA... |
613 |
or the Intel Wired Networking project hosted by Sourceforge at: |
55be062d2 e1000: update the... |
614 615 |
http://sourceforge.net/projects/e1000 |
1da177e4c Linux-2.6.12-rc2 |
616 |
If an issue is identified with the released source code on the supported |
55be062d2 e1000: update the... |
617 |
kernel with a supported adapter, email the specific information related |
de3edab42 e1000: update REA... |
618 |
to the issue to e1000-devel@lists.sf.net |