e100.rst 6.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185
  1. .. SPDX-License-Identifier: GPL-2.0+
  2. =============================================================
  3. Linux Base Driver for the Intel(R) PRO/100 Family of Adapters
  4. =============================================================
  5. June 1, 2018
  6. Contents
  7. ========
  8. - In This Release
  9. - Identifying Your Adapter
  10. - Building and Installation
  11. - Driver Configuration Parameters
  12. - Additional Configurations
  13. - Known Issues
  14. - Support
  15. In This Release
  16. ===============
  17. This file describes the Linux Base Driver for the Intel(R) PRO/100 Family of
  18. Adapters. This driver includes support for Itanium(R)2-based systems.
  19. For questions related to hardware requirements, refer to the documentation
  20. supplied with your Intel PRO/100 adapter.
  21. The following features are now available in supported kernels:
  22. - Native VLANs
  23. - Channel Bonding (teaming)
  24. - SNMP
  25. Channel Bonding documentation can be found in the Linux kernel source:
  26. /Documentation/networking/bonding.rst
  27. Identifying Your Adapter
  28. ========================
  29. For information on how to identify your adapter, and for the latest Intel
  30. network drivers, refer to the Intel Support website:
  31. https://www.intel.com/support
  32. Driver Configuration Parameters
  33. ===============================
  34. The default value for each parameter is generally the recommended setting,
  35. unless otherwise noted.
  36. Rx Descriptors:
  37. Number of receive descriptors. A receive descriptor is a data
  38. structure that describes a receive buffer and its attributes to the network
  39. controller. The data in the descriptor is used by the controller to write
  40. data from the controller to host memory. In the 3.x.x driver the valid range
  41. for this parameter is 64-256. The default value is 256. This parameter can be
  42. changed using the command::
  43. ethtool -G eth? rx n
  44. Where n is the number of desired Rx descriptors.
  45. Tx Descriptors:
  46. Number of transmit descriptors. A transmit descriptor is a data
  47. structure that describes a transmit buffer and its attributes to the network
  48. controller. The data in the descriptor is used by the controller to read
  49. data from the host memory to the controller. In the 3.x.x driver the valid
  50. range for this parameter is 64-256. The default value is 128. This parameter
  51. can be changed using the command::
  52. ethtool -G eth? tx n
  53. Where n is the number of desired Tx descriptors.
  54. Speed/Duplex:
  55. The driver auto-negotiates the link speed and duplex settings by
  56. default. The ethtool utility can be used as follows to force speed/duplex.::
  57. ethtool -s eth? autoneg off speed {10|100} duplex {full|half}
  58. NOTE: setting the speed/duplex to incorrect values will cause the link to
  59. fail.
  60. Event Log Message Level:
  61. The driver uses the message level flag to log events
  62. to syslog. The message level can be set at driver load time. It can also be
  63. set using the command::
  64. ethtool -s eth? msglvl n
  65. Additional Configurations
  66. =========================
  67. Configuring the Driver on Different Distributions
  68. -------------------------------------------------
  69. Configuring a network driver to load properly when the system is started
  70. is distribution dependent. Typically, the configuration process involves
  71. adding an alias line to `/etc/modprobe.d/*.conf` as well as editing other
  72. system startup scripts and/or configuration files. Many popular Linux
  73. distributions ship with tools to make these changes for you. To learn
  74. the proper way to configure a network device for your system, refer to
  75. your distribution documentation. If during this process you are asked
  76. for the driver or module name, the name for the Linux Base Driver for
  77. the Intel PRO/100 Family of Adapters is e100.
  78. As an example, if you install the e100 driver for two PRO/100 adapters
  79. (eth0 and eth1), add the following to a configuration file in
  80. /etc/modprobe.d/::
  81. alias eth0 e100
  82. alias eth1 e100
  83. Viewing Link Messages
  84. ---------------------
  85. In order to see link messages and other Intel driver information on your
  86. console, you must set the dmesg level up to six. This can be done by
  87. entering the following on the command line before loading the e100
  88. driver::
  89. dmesg -n 6
  90. If you wish to see all messages issued by the driver, including debug
  91. messages, set the dmesg level to eight.
  92. NOTE: This setting is not saved across reboots.
  93. ethtool
  94. -------
  95. The driver utilizes the ethtool interface for driver configuration and
  96. diagnostics, as well as displaying statistical information. The ethtool
  97. version 1.6 or later is required for this functionality.
  98. The latest release of ethtool can be found from
  99. https://www.kernel.org/pub/software/network/ethtool/
  100. Enabling Wake on LAN (WoL)
  101. --------------------------
  102. WoL is provided through the ethtool utility. For instructions on
  103. enabling WoL with ethtool, refer to the ethtool man page. WoL will be
  104. enabled on the system during the next shut down or reboot. For this
  105. driver version, in order to enable WoL, the e100 driver must be loaded
  106. when shutting down or rebooting the system.
  107. NAPI
  108. ----
  109. NAPI (Rx polling mode) is supported in the e100 driver.
  110. See :ref:`Documentation/networking/napi.rst <napi>` for more information.
  111. Multiple Interfaces on Same Ethernet Broadcast Network
  112. ------------------------------------------------------
  113. Due to the default ARP behavior on Linux, it is not possible to have one
  114. system on two IP networks in the same Ethernet broadcast domain
  115. (non-partitioned switch) behave as expected. All Ethernet interfaces
  116. will respond to IP traffic for any IP address assigned to the system.
  117. This results in unbalanced receive traffic.
  118. If you have multiple interfaces in a server, either turn on ARP
  119. filtering by
  120. (1) entering::
  121. echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter
  122. (this only works if your kernel's version is higher than 2.4.5), or
  123. (2) installing the interfaces in separate broadcast domains (either
  124. in different switches or in a switch partitioned to VLANs).
  125. Support
  126. =======
  127. For general information, go to the Intel support website at:
  128. https://www.intel.com/support/
  129. If an issue is identified with the released source code on a supported kernel
  130. with a supported adapter, email the specific information related to the issue
  131. to intel-wired-lan@lists.osuosl.org.