Lines Matching refs:the
22 the e1000 driver, not the e1000e driver due to the 82546 part being used
25 For more information on how to identify your adapter, go to the Adapter &
30 For the latest Intel network drivers for Linux, refer to the following
31 website. In the search field, enter your adapter name or type, or use the
32 networking link on the left to search for your adapter:
39 The default value for each parameter is generally the recommended setting,
42 NOTES: For more information about the InterruptThrottleRate,
44 parameters, see the application note at:
53 The driver can limit the amount of interrupts per second that the adapter
54 will generate for incoming packets. It does this by writing a value to the
55 adapter that is based on the maximum amount of interrupts that the adapter
59 will program the adapter to send out a maximum of that many interrupts
61 load on the system and can lower CPU utilization under heavy load,
64 The default behaviour of the driver previously assumed a static
71 it dynamically adjusts the InterruptThrottleRate value based on the traffic
72 that it receives. After determining the type of incoming traffic in the last
73 timeframe, it will adjust the InterruptThrottleRate to an appropriate value
76 The algorithm classifies the incoming traffic every interval into
77 classes. Once the class is determined, the InterruptThrottleRate value is
78 adjusted to suit that traffic type the best. There are three classes defined:
84 In dynamic conservative mode, the InterruptThrottleRate value is set to 4000
85 for traffic that falls in class "Bulk traffic". If traffic falls in the "Low
86 latency" or "Lowest latency" class, the InterruptThrottleRate is increased
90 grid computing, the algorithm can reduce latency even more when
92 the same as mode 3, the InterruptThrottleRate will be increased stepwise to
95 In simplified mode the interrupt rate is based on the ratio of TX and
96 RX traffic. If the bytes per second rate is approximately equal, the
97 interrupt rate will drop as low as 2000 interrupts per second. If the
98 traffic is mostly transmit or mostly receive, the interrupt rate could
105 NOTE: InterruptThrottleRate takes precedence over the TxAbsIntDelay and
106 RxAbsIntDelay parameters. In other words, minimizing the receive
107 and/or transmit absolute delays does not force the controller to
108 generate more interrupts than what the Interrupt Throttle Rate
112 are in use simultaneously, the CPU utilization may increase non-
113 linearly. In order to limit the CPU utilization without impacting
114 the overall throughput, we recommend that you load the driver as
119 This sets the InterruptThrottleRate to 3000 interrupts/sec for
120 the first, second, and third instances of the driver. The range
122 systems and is a good starting point, but the optimal value will
131 This value delays the generation of receive interrupts in units of 1.024
134 extra latency to frame reception and can end up decreasing the throughput
135 of TCP traffic. If the system is reporting dropped receives, this value
136 may be set too high, causing the driver to run out of available receive
141 this occurs a NETDEV WATCHDOG message is logged in the system
142 event log. In addition, the controller is automatically reset,
143 restoring the network connection. To eliminate the potential
144 for the hang ensure that RxIntDelay is set to 0.
151 This value, in units of 1.024 microseconds, limits the delay in which a
153 this value ensures that an interrupt is generated after the initial
154 packet is received within the set amount of time. Proper tuning,
163 This value delays the generation of transmit interrupts in units of
165 efficiency if properly tuned for specific network traffic. If the
167 causing the driver to run out of available transmit descriptors.
174 This value, in units of 1.024 microseconds, limits the delay in which a
176 this value ensures that an interrupt is generated after the initial
177 packet is sent on the wire within the set amount of time. Proper tuning,
187 buffer before handing it up the stack.
207 This workaround skips resetting the PHY at shutdown for the initial
215 Allows changing the interrupt mode at module load time, without requiring a
216 recompile. If the driver load fails to enable a specific interrupt mode, the
226 Strip the CRC from received packets before sending up the network stack. If
228 loading or enabling the driver, try disabling this feature.
235 If set to 1, configure the hardware to ignore all write/erase cycles to the
236 GbE region in the ICHx NVM (in order to prevent accidental corruption of the
237 NVM). This feature can be disabled by setting the parameter to 0 during initial
240 via setting the parameter to zero. Once the NVM has been locked (via the
241 parameter at 1 when the driver loads) it cannot be unlocked except via power
249 Jumbo Frames support is enabled by changing the MTU to a value larger than
250 the default of 1500. Use the ifconfig command to increase the MTU size.
260 with the maximum Jumbo Frames size of 9234 bytes.
269 MACSec is enabled on the system.
273 The driver utilizes the ethtool interface for driver configuration and
275 strongly recommend downloading the latest version of ethtool at:
284 Speed and Duplex are configured through the ethtool* utility. For
285 instructions, refer to the ethtool man page.
289 WoL is configured through the ethtool* utility. For instructions on
290 enabling WoL with ethtool, refer to the ethtool man page.
292 WoL will be enabled on the system during the next shut down or reboot.
293 For this driver version, in order to enable WoL, the e1000e driver must be
294 loaded when shutting down or rebooting the system.
302 For general information, go to the Intel support website at:
306 or the Intel Wired Networking project hosted by Sourceforge at:
310 If an issue is identified with the released source code on the supported
311 kernel with a supported adapter, email the specific information related
312 to the issue to e1000-devel@lists.sf.net