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