Skip to content

Commit

Permalink
Intel official release 4.3.9
Browse files Browse the repository at this point in the history
  • Loading branch information
@jbrandeb
jbrandeb committed Mar 23, 2024
1 parent 625d80d commit 3969848
Show file tree
Hide file tree
Showing 21 changed files with 488 additions and 660 deletions.
112 changes: 79 additions & 33 deletions README
View file
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,14 @@ result of not disabling LRO when combined with ip forwarding or bridging can be
low throughput or even a kernel panic.


Do not unload port driver if VF with active VM is bound to it
-------------------------------------------------------------

Do not unload a port's driver if a Virtual Function (VF) with an active Virtual
Machine (VM) is bound to it. Doing so will cause the port to appear to hang.
Once the VM shuts down, or otherwise releases the VF, the command will complete.


Configuring SR-IOV for improved network security
------------------------------------------------

Expand Down Expand Up @@ -98,7 +106,7 @@ Configurations later in this document.

Identifying Your Adapter
------------------------
The driver in this release is compatible with 82598, 82599, X540,
The driver in this release is compatible with 82598, 82599, X540, x550,
and X552-based Intel Ethernet Network Connections and Adapters.

For information on how to identify your adapter, go to the Adapter &
Expand Down Expand Up @@ -262,7 +270,7 @@ NOTES:
4. Compile the driver module:
# make install
The binary will be installed as:
/lib/modules/<KERNEL VERSION>/kernel/drivers/net/ixgbe/ixgbe.[k]o
/lib/modules/<KERNEL VERSION>/updates/drivers/net/ethernet/intel/ixgbe/ixgbe.ko

The install location listed above is the default location. This may differ
for various Linux distributions.
Expand Down Expand Up @@ -348,6 +356,7 @@ Valid Range: 0, 1
1 = Enables DCA support in the driver
If the driver is enabled for DCA, this parameter allows load-time control of
the feature.
Note: DCA is not supported on X550-based adapters.


IntMode
Expand All @@ -374,7 +383,7 @@ increased CPU utilization, though it may help throughput in some circumstances.
suitable for bulk throughput traffic due to the increased CPU utilization
of the higher interrupt rate.
NOTES:
- On 82599, X540, disabling InterruptThrottleRate
- On 82599, and X540, and X550-based adapters, disabling InterruptThrottleRate
will also result in the driver disabling HW RSC.
- On 82598-based adapters, disabling InterruptThrottleRate will also
result in disabling LRO (Large Receive Offloads).
Expand All @@ -399,6 +408,8 @@ packets that match certain criteria as set by the parameters described below.
LLI parameters are not enabled when Legacy interrupts are used. You must be
using MSI or MSI-X (see cat /proc/interrupts) to successfully use LLI.

Note: LLI is not supported on X550-based adapters.


LLIPort
-------
Expand All @@ -411,6 +422,8 @@ WARNING: Enabling LLI can result in an excessive number of interrupts/second
that may cause problems with the system and in some cases may cause a kernel
panic.

Note: LLI is not supported on X550-based adapters.


LLIPush
-------
Expand All @@ -419,19 +432,25 @@ LLIPush can be set to be enabled or disabled (default). It is most effective
in an environment with many small transactions.
NOTE: Enabling LLIPush may allow a denial of service attack.

Note: LLI is not supported on X550-based adapters.


LLISize
-------
Valid Range: 0-1500
LLISize causes an immediate interrupt if the board receives a packet smaller
than the specified size.

Note: LLI is not supported on X550-based adapters.


LLIEType
--------
Valid Range: 0-0x8FFF
This parameter specifies the Low Latency Interrupt (LLI) Ethernet protocol type.

Note: LLI is not supported on X550-based adapters.


LLIVLANP
--------
Expand All @@ -440,6 +459,8 @@ Valid Range: 0-7

This parameter specifies the LLI on VLAN priority threshold.

Note: LLI is not supported on X550-based adapters.


Flow Control
------------
Expand Down Expand Up @@ -483,6 +504,13 @@ NOTES:
transmit queues.
- An included script (set_irq_affinity) automates setting the IRQ to
CPU affinity.
- Flow director masking works in the opposite manner from subnet masking. In
the following command:
#ethtool -N eth11 flow-type ip4 src-ip 172.4.1.2 m 255.0.0.0 dst-ip \
172.21.1.1 m 255.128.0.0 action 31
The src-ip value that is written to the filter will be 0.4.1.2, not
172.0.0.0 as might be expected. Similarly, the dst-ip value written to the
filter will be 0.21.1.1, not 172.0.0.0.

ethtool commands:

Expand Down Expand Up @@ -541,7 +569,8 @@ Support for UDP RSS
This feature adds an ON/OFF switch for hashing over certain flow types. Only
UDP can be turned on. The default setting is disabled.

Only support for enabling/disabling hashing on ports for UDP over IPv4 (UDP4) or IPv6 (UDP6) is supported.
Only support for enabling/disabling hashing on ports for UDP over IPv4 (UDP4) or
IPv6 (UDP6) is supported.

NOTE: Fragmented packets may arrive out of order when RSS UDP support is
configured.
Expand Down Expand Up @@ -608,7 +637,7 @@ indicates that ATR should be disabled and no samples will be taken.

max_vfs
-------
Valid Range: 1-
Valid Range: 1-63
If the value is greater than 0 it will also force the VMDq parameter to be 1
or more.

Expand All @@ -618,17 +647,18 @@ and above, use sysfs to enable VFs. For example:
#echo 0 > /sys/class/net/$dev/device/sriov_numvfs //disable VFs

The parameters for the driver are referenced by position. Thus, if you have a
dual port adapter, or more than one adapter in your system, and want N virtual functions per port, you must specify a
number for each port with each parameter separated by a comma. For example:
dual port adapter, or more than one adapter in your system, and want N virtual
functions per port, you must specify a number for each port with each parameter
separated by a comma. For example:
modprobe ixgbe max_vfs=4,1
NOTE: Caution must be used in loading the driver with these parameters.
Depending on your system configuration, number of slots, etc., it is impossible
to predict in all cases where the positions would be on the command line.
This parameter adds support for SR-IOV. It causes the driver to spawn up to
max_vfs worth of virtual functions.
NOTE: When either SR-IOV mode or VMDq mode is enabled, hardware VLAN filtering
and VLAN tag stripping/insertion will remain enabled. Please remove the old
VLAN filter before the new VLAN filter is added. For example,
NOTE: When either SR-IOV mode or VMDq mode is enabled, hardware VLAN
filtering and VLAN tag stripping/insertion will remain enabled. Please remove
the old VLAN filter before the new VLAN filter is added. For example,
ip link set eth0 vf 0 vlan 100 // set vlan 100 for VF 0
ip link set eth0 vf 0 vlan 0 // Delete vlan 100
ip link set eth0 vf 0 vlan 200 // set a new vlan 200 for VF 0
Expand Down Expand Up @@ -754,16 +784,16 @@ A whitepaper containing information on how to best configure your platform is
available on the Intel website.


EEE
---
Valid Range: 0-1
0 = Disables EEE
1 = Enables EEE
A link between two EEE-compliant devices will result in periodic bursts of
data followed by periods where the link is in an idle state. This Low Power
Idle (LPI) state is supported in both 1 Gbps and 10 Gbps link speeds.
AQRate
------

NOTE: EEE support requires auto-negotiation.
Devices that support AQRate (X550 and later) will include 2.5 Gbps and
5 Gbps in the speeds that the driver advertises during auto-negotiation,
even though ethtool will not display 2.5 Gbps or 5 Gbps as "Supported link
modes" or "Advertised link modes." These speeds are only available through
unmodified auto-negotiation. You cannot use ethtool -s advertise to force
auto-negotiation to advertise 2.5 Gbps or 5 Gbps. If a 2.5 Gbps or 5 Gbps
link is created, ethtool will report the correct link speed.


================================================================================
Expand Down Expand Up @@ -870,11 +900,11 @@ the desired speed.
Hardware Receive Side Coalescing (HW RSC)
-----------------------------------------

82599 and X540-based adapters support HW RSC, which can merge multiple
82599 and X540, and X550-based adapters support HW RSC, which can merge multiple
frames from the same IPv4 TCP/IP flow into a single structure that can span
one or more descriptors. It works similarly to Software Large Receive Offload
technique. By default HW RSC is enabled and SW LRO cannot be used for 82599
or X540-based adapters unless HW RSC is disabled.
or X540, or X550-based adapters unless HW RSC is disabled.

IXGBE_NO_HW_RSC is a compile time flag. The user can enable it at compile time
to remove support for HW RSC from the driver. The flag is used by adding
Expand Down Expand Up @@ -919,6 +949,13 @@ Some adapters do not support Wake on LAN. To determine if your adapter
supports Wake on LAN, run
ethtool ethX

The Intel(R) Ethernet Converged Network Adapter X550-T1 and Intel(R) Ethernet
Converged Network Adapter X550-T2 have a manageability/AUX power connector.
These devices only support WoL if AUX power is supplied via this connector.
Note that this is system and adapter specific. Some with this connector do not
support WoL. Some systems do not provide the correct power connection. See your
system documentation for details.


IEEE 1588 Precision Time Protocol (PTP) Hardware Clock (PHC)
------------------------------------------------------------
Expand All @@ -936,19 +973,28 @@ as follows when it is being compiled:
VXLAN Overlay HW Offloading
---------------------------

VXLAN Overlay HW Offloading is enabled by default. The ixgbe Linux driver
features VXLAN Overlay HW Offloading support. To view and configure
VXLAN on a VXLAN-overlay offload enabled device, use the following
commands:
Virtual Extensible LAN (VXLAN) allows you to extend an L2 network over an L3
network, which may be useful in a virtualized or cloud environment. Some Intel(R)
Ethernet Network devices perform VXLAN processing, offloading it from the
operating system. This reduces CPU utilization.

VXLAN offloading is controlled by the tx and rx checksum offload options
provided by ethtool. That is, if tx checksum offload is enabled, and the adapter
has the capability, VXLAN offloading is also enabled. If rx checksum offload is
enabled, then the VXLAN packets rx checksum will be offloaded, unless the module
parameter vxlan_rx=0,0 was used to specifically disable the VXLAN rx offload.

VXLAN Overlay HW Offloading is enabled by default. To view and configure VXLAN
on a VXLAN-overlay offload enabled device, use the following
command:

# ethtool -k ethX
(This command displays the offloads and their current state.)
# ethtool -K ethX tx-udp_tnl-segmentation [off|on]
(This enables/disables VXLAN support in the driver.)

For more information on configuring your network for VXLAN overlay support,
refer to the Intel Technical Brief, "Creating Overlay Networks Using Intel
Ethernet Converged Network Adapters" (Intel Networking Division, August 2013):
For more information on configuring your network for overlay HW offloading
support, refer to the Intel Technical Brief, "Creating Overlay Networks
Using Intel Ethernet Converged Network Adapters" (Intel Networking Division,
August 2013):

http://www.intel.com/content/dam/www/public/us/en/documents/technology-briefs/
overlay-networks-using-converged-network-adapters-brief.pdf
Expand Down Expand Up @@ -1094,7 +1140,7 @@ queues on a platform with more than 16 cores.
Due to known hardware limitations, RSS can only filter in a maximum of 16
receive queues.

82599 and X540-based network connections support up to 64 queues.
82599 and X540, and X550-based network connections support up to 64 queues.


Disable GRO when routing/bridging
Expand Down Expand Up @@ -1241,10 +1287,10 @@ For general information, go to the Intel support website at:
www.intel.com/support/

or the Intel Wired Networking project hosted by Sourceforge at:
http://sourceforge.net/projects/ixgbe
http://sourceforge.net/projects/e1000
If an issue is identified with the released source code on a supported
kernel with a supported adapter, email the specific information related to the
issue to ixgbe[email protected].
issue to e1000[email protected].


================================================================================
Expand Down
101 changes: 51 additions & 50 deletions SUMS
View file
Original file line number Diff line number Diff line change
@@ -1,50 +1,51 @@
64680 49 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/README
26627 8 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_phy.h
64076 42 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_sriov.c
25929 7 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_osdep.h
64113 86 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_x550.c
12190 1 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/Module.supported
33819 77 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_82599.c
60138 4 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_sriov.h
55717 74 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_phy.c
23422 3 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_x540.h
18855 134 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_common.c
41259 10 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_api.h
11744 33 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_param.c
53485 20 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_dcb.c
32187 298 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_main.c
54301 8 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_debugfs.c
53143 6 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_dcb.h
16759 17 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_dcb_82599.c
54750 3 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_fcoe.h
38247 5 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_dcb_82599.h
41090 29 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_fcoe.c
00986 29 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_x540.c
10210 8 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_sysfs.c
10208 46 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_api.c
21099 10 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_dcb_82598.c
10067 23 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_dcb_nl.c
04046 40 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_82598.c
30041 13 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/Makefile
10046 2 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_82598.h
03018 4 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_dcb_82598.h
42997 7 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_mbx.h
58442 20 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_mbx.c
29344 140 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/kcompat.h
14576 27 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_procfs.c
18269 36 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe.h
02089 2 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_osdep2.h
56780 8 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_common.h
36107 52 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/kcompat.c
27260 3 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_82599.h
53472 106 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_ethtool.c
33230 45 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_ptp.c
04610 158 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_type.h
29498 5 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_x550.h
43358 37 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/ixgbe_lib.c
19027 29 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/src/kcompat_ethtool.c
09576 6 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/scripts/set_irq_affinity
47928 10 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/ixgbe.spec
52231 7 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/pci.updates
42571 18 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/COPYING
32863 9 /tmp/tmp.iAIJbZ4160/ixgbe-4.2.5/ixgbe.7
07264 36 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe.h
32870 7 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/Makefile
18855 134 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_common.c
56780 8 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_common.h
34698 104 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_ethtool.c
35395 8 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/common.mk
34409 33 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_param.c
25929 7 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_osdep.h
04046 40 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_82598.c
10046 2 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_82598.h
49645 77 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_82599.c
27260 3 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_82599.h
10208 46 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_api.c
41259 10 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_api.h
53485 20 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_dcb.c
53143 6 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_dcb.h
43358 37 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_lib.c
58442 20 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_mbx.c
14415 7 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_mbx.h
32269 74 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_phy.c
26627 8 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_phy.h
33230 45 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_ptp.c
14576 27 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_procfs.c
54301 8 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_debugfs.c
41090 29 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_fcoe.c
54750 3 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_fcoe.h
02089 2 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_osdep2.h
35351 298 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_main.c
21099 10 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_dcb_82598.c
03018 4 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_dcb_82598.h
16759 17 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_dcb_82599.c
38247 5 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_dcb_82599.h
17186 40 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_sriov.c
55721 4 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_sriov.h
10067 23 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_dcb_nl.c
35811 52 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/kcompat.c
34106 139 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/kcompat.h
00324 29 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_x540.c
23422 3 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_x540.h
00776 87 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_x550.c
29498 5 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_x550.h
09034 158 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_type.h
19027 29 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/kcompat_ethtool.c
10210 8 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/ixgbe_sysfs.c
12190 1 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/src/Module.supported
44189 9 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/ixgbe.7
49485 51 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/README
09576 6 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/scripts/set_irq_affinity
30987 10 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/ixgbe.spec
44149 7 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/pci.updates
42571 18 /tmp/tmp.EpxZMT5244/ixgbe-4.3.9/COPYING
Loading

0 comments on commit 3969848

Please sign in to comment.