ethernet/intel/e1000.rst

1 .. SPDX-License-Identifier: GPL-2.0+
8 Copyright(c) 1999 - 2013 Intel Corporation.
13 - Identifying Your Adapter
14 - Command Line Parameters
15 - Speed and Duplex Configuration
16 - Additional Configurations
17 - Support
50 -------
54 :Valid Range:   0x01-0x0F, 0x20-0x2F
57 This parameter is a bit-mask that specifies the speed and duplex settings
66 ------
70 :Valid Range:   0-2 (0=auto-negotiate, 1=half, 2=full)
74 either one or two-directional.  If both Duplex and the link partner are
75 set to auto-negotiate, the board auto-detects the correct duplex.  If the
76 link partner is forced (either full or half), Duplex defaults to half-
80 -----------
82 :Valid Range:   0-3 (0=none, 1=Rx only, 2=Tx only, 3=Rx&Tx)
89 ---------------------
91 (not supported on Intel(R) 82542, 82543 or 82544-based adapters)
94    0,1,3,4,100-100000 (0=off, 1=dynamic, 3=dynamic conservative,
107 but will increase latency as packets are not processed as quickly.
111 all traffic types,but lacking in small packet performance and latency.
124 "Bulk traffic", for large amounts of packets of normal size; "Low latency",
126 packets; and "Lowest latency", for almost completely small packets or
130 for traffic that falls in class "Bulk traffic". If traffic falls in the "Low
131 latency" or "Lowest latency" class, the InterruptThrottleRate is increased
134 For situations where low latency is vital such as cluster or
135 grid computing, the algorithm can reduce latency even more when
138 70000 for traffic in class "Lowest latency".
142 interrupt rate will drop as low as 2000 interrupts per second.  If the
147 and may improve small packet latency, but is generally not suitable
170        are in use simultaneously, the CPU utilization may increase non-
181        be platform-specific.  If CPU utilization is not a concern, use
185 -------------
188  - 48-256 for 82542 and 82543-based adapters
189  - 48-4096 for all other supported adapters
207 ----------
209 :Valid Range:   0-65535 (0=off)
215 extra latency to frame reception and can end up decreasing the throughput
229 -------------
233 :Valid Range:   0-65535 (0=off)
237 receive interrupt is generated.  Useful only if RxIntDelay is non-zero,
244 -----
249 :Default Value:  0 (auto-negotiate at all supported speeds)
253 partner is set to auto-negotiate, the board will auto-detect the correct
257 -------------
260   - 48-256 for 82542 and 82543-based adapters
261   - 48-4096 for all other supported adapters
274 ----------
276 :Valid Range:   0-65535 (0=off)
286 -------------
290 :Valid Range:   0-65535 (0=off)
294 transmit interrupt is generated.  Useful only if TxIntDelay is non-zero,
301 ------
303 (This parameter is NOT supported on the 82542-based adapter.)
305 :Valid Range:   0-1
312 ---------
314 :Valid Range:   0-xxxxxxx (0=off)
327 --------------------
329 :Valid Range: 0-1
342 fiber interface board only links at 1000 Mbps full-duplex.
344 For copper-based boards, the keywords interact as follows:
346 - The default operation is auto-negotiate.  The board advertises all
348   common speed and duplex mode IF the link partner is set to auto-negotiate.
350 - If Speed = 1000, limited auto-negotiation is enabled and only 1000 Mbps
351   is advertised (The 1000BaseT spec requires auto-negotiation.)
353 - If Speed = 10 or 100, then both Speed and Duplex should be set.  Auto-
358 auto-negotiation process.  It should be used when you wish to control which
359 speed and duplex combinations are advertised during the auto-negotiation
395 ------------
408   to the file /etc/sysconfig/network-scripts/ifcfg-eth<x>.  This example
417   networking/ip-sysctl.txt for more details.
419   - The maximum MTU setting for Jumbo Frames is 16110.  This value coincides
422   - Using Jumbo frames at 10 or 100 Mbps is not supported and may result in
425   - Adapters based on the Intel(R) 82542 and 82573V/E controller do not
432 -------
442 --------------------------
458 to the issue to intel-wired-lan@lists.osuosl.org.