diff options
| -rw-r--r-- | Documentation/networking/e100.rst | 115 |
1 files changed, 58 insertions, 57 deletions
diff --git a/Documentation/networking/e100.rst b/Documentation/networking/e100.rst index 59b80608e27d..9708f5fa76de 100644 --- a/Documentation/networking/e100.rst +++ b/Documentation/networking/e100.rst | |||
| @@ -87,83 +87,84 @@ Event Log Message Level: The driver uses the message level flag to log events | |||
| 87 | Additional Configurations | 87 | Additional Configurations |
| 88 | ========================= | 88 | ========================= |
| 89 | 89 | ||
| 90 | Configuring the Driver on Different Distributions | 90 | Configuring the Driver on Different Distributions |
| 91 | ------------------------------------------------- | 91 | ------------------------------------------------- |
| 92 | 92 | ||
| 93 | Configuring a network driver to load properly when the system is started is | 93 | Configuring a network driver to load properly when the system is started |
| 94 | distribution dependent. Typically, the configuration process involves adding | 94 | is distribution dependent. Typically, the configuration process involves |
| 95 | an alias line to /etc/modprobe.d/*.conf as well as editing other system | 95 | adding an alias line to /etc/modprobe.d/*.conf as well as editing other |
| 96 | startup scripts and/or configuration files. Many popular Linux | 96 | system startup scripts and/or configuration files. Many popular Linux |
| 97 | distributions ship with tools to make these changes for you. To learn the | 97 | distributions ship with tools to make these changes for you. To learn |
| 98 | proper way to configure a network device for your system, refer to your | 98 | the proper way to configure a network device for your system, refer to |
| 99 | distribution documentation. If during this process you are asked for the | 99 | your distribution documentation. If during this process you are asked |
| 100 | driver or module name, the name for the Linux Base Driver for the Intel | 100 | for the driver or module name, the name for the Linux Base Driver for |
| 101 | PRO/100 Family of Adapters is e100. | 101 | the Intel PRO/100 Family of Adapters is e100. |
| 102 | 102 | ||
| 103 | As an example, if you install the e100 driver for two PRO/100 adapters | 103 | As an example, if you install the e100 driver for two PRO/100 adapters |
| 104 | (eth0 and eth1), add the following to a configuration file in /etc/modprobe.d/ | 104 | (eth0 and eth1), add the following to a configuration file in |
| 105 | /etc/modprobe.d/:: | ||
| 105 | 106 | ||
| 106 | alias eth0 e100 | 107 | alias eth0 e100 |
| 107 | alias eth1 e100 | 108 | alias eth1 e100 |
| 108 | 109 | ||
| 109 | Viewing Link Messages | 110 | Viewing Link Messages |
| 110 | --------------------- | 111 | --------------------- |
| 111 | In order to see link messages and other Intel driver information on your | ||
| 112 | console, you must set the dmesg level up to six. This can be done by | ||
| 113 | entering the following on the command line before loading the e100 driver:: | ||
| 114 | 112 | ||
| 115 | dmesg -n 6 | 113 | In order to see link messages and other Intel driver information on your |
| 116 | 114 | console, you must set the dmesg level up to six. This can be done by | |
| 117 | If you wish to see all messages issued by the driver, including debug | 115 | entering the following on the command line before loading the e100 |
| 118 | messages, set the dmesg level to eight. | 116 | driver:: |
| 119 | 117 | ||
| 120 | NOTE: This setting is not saved across reboots. | 118 | dmesg -n 6 |
| 121 | 119 | ||
| 120 | If you wish to see all messages issued by the driver, including debug | ||
| 121 | messages, set the dmesg level to eight. | ||
| 122 | 122 | ||
| 123 | ethtool | 123 | NOTE: This setting is not saved across reboots. |
| 124 | ------- | ||
| 125 | 124 | ||
| 126 | The driver utilizes the ethtool interface for driver configuration and | 125 | ethtool |
| 127 | diagnostics, as well as displaying statistical information. The ethtool | 126 | ------- |
| 128 | version 1.6 or later is required for this functionality. | ||
| 129 | 127 | ||
| 130 | The latest release of ethtool can be found from | 128 | The driver utilizes the ethtool interface for driver configuration and |
| 131 | https://www.kernel.org/pub/software/network/ethtool/ | 129 | diagnostics, as well as displaying statistical information. The ethtool |
| 130 | version 1.6 or later is required for this functionality. | ||
| 132 | 131 | ||
| 133 | Enabling Wake on LAN* (WoL) | 132 | The latest release of ethtool can be found from |
| 134 | --------------------------- | 133 | https://www.kernel.org/pub/software/network/ethtool/ |
| 135 | WoL is provided through the ethtool* utility. For instructions on enabling | ||
| 136 | WoL with ethtool, refer to the ethtool man page. | ||
| 137 | 134 | ||
| 138 | WoL will be enabled on the system during the next shut down or reboot. For | 135 | Enabling Wake on LAN* (WoL) |
| 139 | this driver version, in order to enable WoL, the e100 driver must be | 136 | --------------------------- |
| 140 | loaded when shutting down or rebooting the system. | 137 | WoL is provided through the ethtool* utility. For instructions on |
| 138 | enabling WoL with ethtool, refer to the ethtool man page. WoL will be | ||
| 139 | enabled on the system during the next shut down or reboot. For this | ||
| 140 | driver version, in order to enable WoL, the e100 driver must be loaded | ||
| 141 | when shutting down or rebooting the system. | ||
| 141 | 142 | ||
| 142 | NAPI | 143 | NAPI |
| 143 | ---- | 144 | ---- |
| 144 | 145 | ||
| 145 | NAPI (Rx polling mode) is supported in the e100 driver. | 146 | NAPI (Rx polling mode) is supported in the e100 driver. |
| 146 | 147 | ||
| 147 | See https://wiki.linuxfoundation.org/networking/napi for more information | 148 | See https://wiki.linuxfoundation.org/networking/napi for more |
| 148 | on NAPI. | 149 | information on NAPI. |
| 149 | 150 | ||
| 150 | Multiple Interfaces on Same Ethernet Broadcast Network | 151 | Multiple Interfaces on Same Ethernet Broadcast Network |
| 151 | ------------------------------------------------------ | 152 | ------------------------------------------------------ |
| 152 | 153 | ||
| 153 | Due to the default ARP behavior on Linux, it is not possible to have | 154 | Due to the default ARP behavior on Linux, it is not possible to have one |
| 154 | one system on two IP networks in the same Ethernet broadcast domain | 155 | system on two IP networks in the same Ethernet broadcast domain |
| 155 | (non-partitioned switch) behave as expected. All Ethernet interfaces | 156 | (non-partitioned switch) behave as expected. All Ethernet interfaces |
| 156 | will respond to IP traffic for any IP address assigned to the system. | 157 | will respond to IP traffic for any IP address assigned to the system. |
| 157 | This results in unbalanced receive traffic. | 158 | This results in unbalanced receive traffic. |
| 158 | 159 | ||
| 159 | If you have multiple interfaces in a server, either turn on ARP | 160 | If you have multiple interfaces in a server, either turn on ARP |
| 160 | filtering by | 161 | filtering by |
| 161 | 162 | ||
| 162 | (1) entering:: echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter | 163 | (1) entering:: echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter |
| 163 | (this only works if your kernel's version is higher than 2.4.5), or | 164 | (this only works if your kernel's version is higher than 2.4.5), or |
| 164 | 165 | ||
| 165 | (2) installing the interfaces in separate broadcast domains (either | 166 | (2) installing the interfaces in separate broadcast domains (either |
| 166 | in different switches or in a switch partitioned to VLANs). | 167 | in different switches or in a switch partitioned to VLANs). |
| 167 | 168 | ||
| 168 | 169 | ||
| 169 | Support | 170 | Support |
