Lines Matching refs:may
149 dropped receives, this value may be set too high, causing the driver to
188 behavior after modifying this register may be undefined (possibly errors of
190 back to 22 (setpci -d 8086:1a48 e6.b=22) may be required to get back to a
211 # some of the defaults may be different for your kernel
214 # several network benchmark tests, your mileage may vary
342 Excessive CRC errors may be observed if the Intel(R) PRO/10GbE CX4
345 The CRC errors may be received either by the Intel(R) PRO/10GbE CX4
347 cable assembly may resolve the issue.
352 Excessive CRC errors may be observed if the Intel(R) PRO/10GbE CX4 Server
354 (1 m or shorter). If this situation occurs, using a longer cable may resolve
357 Excessive CRC errors may be observed using Fujitsu 24AWG cable assemblies that
359 errors may be received either by the CX4 Server adapter or at the switch. If
360 this situation occurs, using a different cable assembly may resolve the issue.
367 Frames, your system may require more than the advertised minimum
373 Degradation in throughput performance may be observed in some Jumbo frames
375 size and/or increasing the /proc/sys/net/ipv4/tcp_*mem entry values may help.
382 Allocating Rx buffers when using Jumbo Frames on 2.6.x kernels may fail if
383 the available memory is heavily fragmented. This issue may be seen with PCI-X
409 may drop UDP packets due to the fullness of socket buffers. You may want
417 "ethtool -K eth0 tso off" may resolve the problem.