igb.txt 4.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132
  1. Linux* Base Driver for Intel(R) Network Connection
  2. ==================================================
  3. Intel Gigabit Linux driver.
  4. Copyright(c) 1999 - 2010 Intel Corporation.
  5. Contents
  6. ========
  7. - Identifying Your Adapter
  8. - Additional Configurations
  9. - Support
  10. Identifying Your Adapter
  11. ========================
  12. This driver supports all 82575, 82576 and 82580-based Intel (R) gigabit network
  13. connections.
  14. For specific information on how to identify your adapter, go to the Adapter &
  15. Driver ID Guide at:
  16. http://support.intel.com/support/go/network/adapter/idguide.htm
  17. Command Line Parameters
  18. =======================
  19. The default value for each parameter is generally the recommended setting,
  20. unless otherwise noted.
  21. max_vfs
  22. -------
  23. Valid Range: 0-7
  24. Default Value: 0
  25. This parameter adds support for SR-IOV. It causes the driver to spawn up to
  26. max_vfs worth of virtual function.
  27. Additional Configurations
  28. =========================
  29. Jumbo Frames
  30. ------------
  31. Jumbo Frames support is enabled by changing the MTU to a value larger than
  32. the default of 1500. Use the ifconfig command to increase the MTU size.
  33. For example:
  34. ifconfig eth<x> mtu 9000 up
  35. This setting is not saved across reboots.
  36. Notes:
  37. - The maximum MTU setting for Jumbo Frames is 9216. This value coincides
  38. with the maximum Jumbo Frames size of 9234 bytes.
  39. - Using Jumbo Frames at 10 or 100 Mbps may result in poor performance or
  40. loss of link.
  41. Ethtool
  42. -------
  43. The driver utilizes the ethtool interface for driver configuration and
  44. diagnostics, as well as displaying statistical information.
  45. http://sourceforge.net/projects/gkernel.
  46. Enabling Wake on LAN* (WoL)
  47. ---------------------------
  48. WoL is configured through the Ethtool* utility.
  49. For instructions on enabling WoL with Ethtool, refer to the Ethtool man page.
  50. WoL will be enabled on the system during the next shut down or reboot.
  51. For this driver version, in order to enable WoL, the igb driver must be
  52. loaded when shutting down or rebooting the system.
  53. Wake On LAN is only supported on port A of multi-port adapters.
  54. Wake On LAN is not supported for the Intel(R) Gigabit VT Quad Port Server
  55. Adapter.
  56. Multiqueue
  57. ----------
  58. In this mode, a separate MSI-X vector is allocated for each queue and one
  59. for "other" interrupts such as link status change and errors. All
  60. interrupts are throttled via interrupt moderation. Interrupt moderation
  61. must be used to avoid interrupt storms while the driver is processing one
  62. interrupt. The moderation value should be at least as large as the expected
  63. time for the driver to process an interrupt. Multiqueue is off by default.
  64. REQUIREMENTS: MSI-X support is required for Multiqueue. If MSI-X is not
  65. found, the system will fallback to MSI or to Legacy interrupts.
  66. LRO
  67. ---
  68. Large Receive Offload (LRO) is a technique for increasing inbound throughput
  69. of high-bandwidth network connections by reducing CPU overhead. It works by
  70. aggregating multiple incoming packets from a single stream into a larger
  71. buffer before they are passed higher up the networking stack, thus reducing
  72. the number of packets that have to be processed. LRO combines multiple
  73. Ethernet frames into a single receive in the stack, thereby potentially
  74. decreasing CPU utilization for receives.
  75. NOTE: You need to have inet_lro enabled via either the CONFIG_INET_LRO or
  76. CONFIG_INET_LRO_MODULE kernel config option. Additionally, if
  77. CONFIG_INET_LRO_MODULE is used, the inet_lro module needs to be loaded
  78. before the igb driver.
  79. You can verify that the driver is using LRO by looking at these counters in
  80. Ethtool:
  81. lro_aggregated - count of total packets that were combined
  82. lro_flushed - counts the number of packets flushed out of LRO
  83. lro_no_desc - counts the number of times an LRO descriptor was not available
  84. for the LRO packet
  85. NOTE: IPv6 and UDP are not supported by LRO.
  86. Support
  87. =======
  88. For general information, go to the Intel support website at:
  89. www.intel.com/support/
  90. or the Intel Wired Networking project hosted by Sourceforge at:
  91. http://sourceforge.net/projects/e1000
  92. If an issue is identified with the released source code on the supported
  93. kernel with a supported adapter, email the specific information related
  94. to the issue to e1000-devel@lists.sf.net