ethernet/intel/iavf.rst

1 .. SPDX-License-Identifier: GPL-2.0+
8 Copyright(c) 2013-2018 Intel Corporation.
13 - Overview
14 - Identifying Your Adapter
15 - Additional Configurations
16 - Known Issues/Troubleshooting
17 - Support
30 The guest OS loading the iavf driver must support MSI-X interrupts.
53 ---------------------
58     # dmesg -n 8
64 -------
71 --------------------------
81     # ethtool -K <if_name> rxvlan on/off
85     # ethtool --offload <if_name> rxvlan on/off
88 -------------------------
99 - 4 Queue Pairs (QP) and associated Configuration Status Registers (CSRs)
101 - i40e descriptors and ring format
102 - Descriptor write-back completion
103 - 1 control queue, with i40e descriptors, CSRs and ring format
104 - 5 MSI-X interrupt vectors and corresponding i40e CSRs
105 - 1 Interrupt Throttle Rate (ITR) index
106 - 1 Virtual Station Interface (VSI) per VF
107 - 1 Traffic Class (TC), TC0
108 - Receive Side Scaling (RSS) with 64 entry indirection table and key,
110 - 1 unicast MAC address reserved per VF
111 - 16 MAC address filters for each VF
112 - Stateless offloads - non-tunneled checksums
113 - AVF device ID
114 - HW mailbox is used for VF to PF communications (including on Windows)
117 ---------------------------
131 NOTES:
135 Application Device Queues (ADq)
136 -------------------------------
137 Application Device Queues (ADq) allows you to dedicate one or more queues to a
138 specific application. This can reduce latency for the specified application,
139 and allow Tx traffic to be rate limited per application. Follow the steps below
144 - The sch_mqprio, act_mirred and cls_flower modules must be loaded
145 - The latest version of iproute2
146 - If another driver (for example, DPDK) has set cloud filters, you cannot
148 - Depending on the underlying PF device, ADQ cannot be enabled when the
168 sets priorities 0-3 to use tc0 and 4-7 to use tc1)
182 monitoring tools such as ``ifstat`` or ``sar -n DEV [interval] [number of samples]``
185   Setting up channels via ethtool (ethtool -L) is not supported when the
190     # ethtool -K <interface> hw-tc-offload on
196 NOTES:
197  - Run all tc commands from the iproute2 <pathtoiproute2>/tc/ directory
198  - ADq is not compatible with cloud filters
199  - Setting up channels via ethtool (ethtool -L) is not supported when the TCs
201  - You must have iproute2 latest version
202  - NVM version 6.01 or later is required
203  - ADq cannot be enabled when any the following features are enabled: Data
205  - If another driver (for example, DPDK) has set cloud filters, you cannot
207  - Tunnel filters are not supported in ADq. If encapsulated packets do arrive
208    in non-tunnel mode, filtering will be done on the inner headers.  For example,
209    for VXLAN traffic in non-tunnel mode, PCTYPE is identified as a VXLAN
212  - If a TC filter on a PF matches traffic over a VF (on the PF), that traffic
216  - If traffic matches multiple TC filters that point to different TCs, that
225 ---------------------------------------------------------------------------------
229 device, when you add a slave, or change the active-backup slave, Linux bonding
235 -------------------------------------------------
243 section "MAC and VLAN anti-spoofing feature" in this readme document.
246 -------------------------------------------------------------
252 --------------------------------
258 --------------------------------------------------
267 ---------------------------------
272     # ethtool -r <PF>
278 ----------------------------------------------------
286 --------------------------
287 The fix to resolve CVE-2016-8105, referenced in Intel SA-00069
288 https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00069.html
292 ------------------------------------------------------
294 on two IP networks in the same Ethernet broadcast domain (non-partitioned
314 -------------------------
326 to intel-wired-lan@lists.osuosl.org.