Enter Serial Adapter Driver E-810 Download

[Lucretia]

PFand VF drivers for the X710 and XL710 server adapters are includedin Red Hat Enterprise Linux, Centos and Ubuntu. 7.x distribution are named i40e and i40evf respectively. Newer versionsof these drivers are available on the Intel Downloads site.

This is an OPTIONAL step for most hypervisors. However, for VMware, upgrading the Intel X710 firmware is a requirement.The Intel E810 firmware must be version is 2.32 or higher. Consult the VMware setup guide for firmware details.

Module options are not persistent from one boot to the next. To ensure that the desired number of VFs are created, eachtime you power cycle the server, append the rc.local file, located in the /etc/rc.d/ directory. The Linux OSexecutes the rc.local script at the end of the boot process. Edit /etc/rc.d/rc.local to initialize the VFs for the driver.

Last year Intel announced a new family of 100 Gigabit network adapters, code-name Columbiaville. These new adapters, based on the new Intel Ethernet Controller E810, support 10/25/50/100 Gbps link speeds and provide programmable offload capabilities.

800 Series adapters implement new features to improve connectivity, storage protocols, and programmability, also thanks to the Dynamic Device Personalization (DDP) technology which adds support for a programmable pipeline. In fact, with DDP, a parser embedded in the controller can support the software parsing custom protocols and manipulating outgoing packets, paving the way to adding new offload capabilities, in addition to those usually available in commodity adapters (e.g. Large Receive Offload, L3/L4 checksum computation, VLAN stripping, etc.). The ability, for instance, to classify custom protocols in hardware and distribute packets to specific queues based on custom packet types, improves the application performance in many use cases. It is possible for instance to extend Receive Side Scaling (RSS) and Flow Director (FDIR) capabilities to be able to inspect encapsulated packet headers as in case of GTP traffic. This was firstly introduced in 700 Series controllers, but with the 800 series it is possible to load custom DDP profiles at boot or during run-time.

The ice-zc driver, introduced a few weeks ago as part of the PF_RING ZC framework, provides Zero-Copy support for 800 Series adapters. Based on initial tests at 100 Gigabit on an Intel Xeon E-2136 CPU @ 3.30GHz, this controller demonstrated to be capable of capturing traffic at 25 Mpps per queue (it scales almost linearly by enabling RSS ) and transmitting almost 90 Mpps by using a single core. On an adequate CPU with enough cores this should let us process 100 Gigabit traffic with multi-process/multi-threaded applications that can leverage on RSS to distribute the load to multiple cores like nProbe Cento. In the above scenario, nProbe Cento processed with 6 RSS queues 78 Mpps (10k flows, 52 Gbit with 64 byte packets or 100 Gbit line rate with larger packets) with no drops making it suitable for low-cost commodity-hardware based packet processing.

Devices based on the Intel(R) Ethernet Controller 800 Series are designed totolerate a limited amount of system latency during PCIe and DMA transactions.If these transactions take longer than the tolerated latency, it can impact thelength of time the packets are buffered in the device and associated memory,which may result in dropped packets. These packets drops typically do not havea noticeable impact on throughput and performance under standard workloads.

In a virtualized environment, on Intel(R) Ethernet Network Adapters thatsupport SR-IOV, the virtual function (VF) may be subject to malicious behavior.Software-generated layer two frames, like IEEE 802.3x (link flow control), IEEE802.1Qbb (priority based flow-control), and others of this type, are notexpected and can throttle traffic between the host and the virtual switch,reducing performance. To resolve this issue, and to ensure isolation fromunintended traffic streams, configure all SR-IOV enabled ports for VLAN taggingfrom the administrative interface on the PF. This configuration allowsunexpected, and potentially malicious, frames to be dropped.

The driver utilizes the ethtool interface for driver configuration anddiagnostics, as well as displaying statistical information. The latest ethtoolversion is required for this functionality. Download it at:

Link messages will not be displayed to the console if the distribution isrestricting system messages. In order to see network driver link messages onyour console, set dmesg to eight by entering the following:

Dynamic Device Personalization (DDP) allows you to change the packet processingpipeline of a device by applying a profile package to the device at runtime.Profiles can be used to, for example, add support for new protocols, changeexisting protocols, or change default settings. DDP profiles can also be rolledback without rebooting the system.

The DDP package loads during device initialization. The driver looks forintel/ice/ddp/ice.pkg in your firmware root (typically /lib/firmware/or /lib/firmware/updates/) and checks that it contains a valid DDP packagefile.

Each flow type supports valid combinations of IP addresses (source ordestination) and UDP/TCP/SCTP ports (source and destination). You can supplyonly a source IP address, a source IP address and a destination port, or anycombination of one or more of these four parameters.

NOTE: This driver allows you to filter traffic based on a user-defined flexibletwo-byte pattern and offset by using the ethtool user-def and mask fields. OnlyL3 and L4 flow types are supported for user-defined flexible filters. For agiven flow type, you must clear all Intel Ethernet Flow Director filters beforechanging the input set (for that flow type).

The second command will fail with an error. You may program multiple filterswith the same fields, using different values, but, on one device, you may notprogram two tcp4 filters with different matching fields.

Note that ICMP headers are parsed as 4 bytes of header and 4 bytes of payload.Thus to match the first byte of the payload, you must actually add 4 bytes tothe offset. Also note that ip4 filters match both ICMP frames as well as raw(unknown) ip4 frames, where the payload will be the L3 payload of the IP4frame.

The maximum offset is 64. The hardware will only read up to 64 bytes of datafrom the payload. The offset must be even because the flexible data is 2 byteslong and must be aligned to byte 0 of the packet payload.

The user-defined flexible offset is also considered part of the input set andcannot be programmed separately for multiple filters of the same type. However,the flexible data is not part of the input set and multiple filters may use thesame offset but match against different data.

Devices based on the Intel(R) Ethernet Controller 800 Series supportAccelerated Receive Flow Steering (aRFS) on the PF. aRFS is a load-balancingmechanism that allows you to direct packets to the same CPU where anapplication is running or consuming the packets in that flow.

The PF driver will display a subset of the statistics for the PF and for allVFs that are configured. The PF will always print a statistics block for eachof the possible VFs, and it will show zero for all unconfigured VFs.

NOTE: Assigning a MAC address for a VF from the host will disable anysubsequent requests to change the MAC address from within the VM. This is asecurity feature. The VM is not aware of this restriction, so if this isattempted in the VM, it will trigger MDD events.

The vf-true-promisc-support private flag does not enable promiscuous mode;rather, it designates which type of promiscuous mode (limited or true) you willget when you enable promiscuous mode using the ip link commands above. Notethat this is a global setting that affects the entire device. However, thevf-true-promisc-support private flag is only exposed to the first PF of thedevice. The PF remains in limited promiscuous mode regardless of thevf-true-promisc-support setting.

Note that the order in which you set the VF to promiscuous mode and add theVLAN interface does not matter (you can do either first). The result in thisexample is that the VF will get all traffic that is tagged with VLAN 100.

In the default mode, an Intel(R) Ethernet Network Adapter using copperconnections will attempt to auto-negotiate with its link partner to determinethe best setting. If the adapter cannot establish link with the link partnerusing auto-negotiation, you may need to manually configure the adapter and linkpartner to identical settings to establish link and pass packets. This shouldonly be needed when attempting to link with an older switch that does notsupport auto-negotiation or one that has been forced to a specific speed orduplex mode. Your link partner must match the setting you choose. 1 Gbps speedsand higher cannot be forced. Use the autonegotiation advertising setting tomanually set devices for 1 Gbps and higher.

Caution: Only experienced network administrators should force speed and duplexor change autonegotiation advertising manually. The settings at the switch mustalways match the adapter settings. Adapter performance may suffer or youradapter may not operate if you configure the adapter differently from yourswitch.

NOTE: The kernel assumes that TC0 is available, and will disable Priority FlowControl (PFC) on the device if TC0 is not available. To fix this, ensure TC0 isenabled when setting up DCB on your switch.

DCB is a configuration Quality of Service implementation in hardware. It usesthe VLAN priority tag (802.1p) to filter traffic. That means that there are 8different priorities that traffic can be filtered into. It also enablespriority flow control (802.1Qbb) which can limit or eliminate the number ofdropped packets during network stress. Bandwidth can be allocated to each ofthese priorities, which is enforced at the hardware level (802.1Qaz).

Ethernet Flow Control (IEEE 802.3x) can be configured with ethtool to enablereceiving and transmitting pause frames for ice. When transmit is enabled,pause frames are generated when the receive packet buffer crosses a predefinedthreshold. When receive is enabled, the transmit unit will halt for the timedelay specified when a pause frame is received.

3a8082e126