- Malicious Device Drive event catch and notify
- Generic flow API
-Prerequisites
--------------
+Linux Prerequisites
+-------------------
- Identifying your adapter using `Intel Support
<http://www.intel.com/support>`_ and get the latest NVM/FW images.
* In all cases Intel recommends using Intel Ethernet Optics; other modules
may function but are not validated by Intel. Contact Intel for supported media types.
+Windows Prerequisites
+---------------------
+
+- Follow the DPDK `Getting Started Guide for Windows <https://doc.dpdk.org/guides/windows_gsg/index.html>`_ to setup the basic DPDK environment.
+
+- Identify the IntelĀ® Ethernet adapter and get the latest NVM/FW version.
+
+- To access any IntelĀ® Ethernet hardware, load the NetUIO driver in place of existing built-in (inbox) driver.
+
+- To load NetUIO driver, follow the steps mentioned in `dpdk-kmods repository
+ <https://git.dpdk.org/dpdk-kmods/tree/windows/netuio/README.rst>`_.
+
Recommended Matching List
-------------------------
Currently hot-plugging of representor ports is not supported so all required
representors must be specified on the creation of the PF.
-- ``Use latest supported vector`` (default ``disable``)
-
- Latest supported vector path may not always get the best perf so vector path was
- recommended to use only on later platform. But users may want the latest vector path
- since it can get better perf in some real work loading cases. So ``devargs`` param
- ``use-latest-supported-vec`` is introduced, for example::
-
- -a 84:00.0,use-latest-supported-vec=1
-
- ``Enable validation for VF message`` (default ``not enabled``)
The PF counts messages from each VF. If in any period of seconds the message
- ``RSS Flow``
RSS Flow supports to set hash input set, hash function, enable hash
- and configure queue region.
+ and configure queues.
For example:
- Configure queue region as queue 0, 1, 2, 3.
+ Configure queues as queue 0, 1, 2, 3.
.. code-block:: console
it will make any cloud filter using inner_vlan or tunnel key invalid. Default configuration will be
recovered only by NIC core reset.
+Mirror rule limitation for X722
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Due to firmware restriction of X722, the same VSI cannot have more than one mirror rule.
+
High Performance of Small Packets on 40GbE NIC
----------------------------------------------