X-Git-Url: http://git.droids-corp.org/?a=blobdiff_plain;f=doc%2Fguides%2Fnics%2Fi40e.rst;h=ef91b3a1ac9f5ea2906c3745563cdfbca1fb4ce5;hb=684ba6265dd24a45e0d797b26a834e8c7bb76716;hp=64f20e7dab0957df658096ca68d32ff8253823c4;hpb=742d9f87f6b8fffb8133099bbc916911d35ee619;p=dpdk.git

diff --git a/doc/guides/nics/i40e.rst b/doc/guides/nics/i40e.rst
index 64f20e7dab..ef91b3a1ac 100644
--- a/doc/guides/nics/i40e.rst
+++ b/doc/guides/nics/i40e.rst
@@ -46,8 +46,8 @@ Features of the i40e PMD are:
 - 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.
@@ -75,6 +75,19 @@ Prerequisites
       * 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 :doc:`guide for Windows <../windows_gsg/run_apps>`
+  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
 -------------------------
 
@@ -88,7 +101,9 @@ For X710/XL710/XXV710,
    +--------------+-----------------------+------------------+
    | DPDK version | Kernel driver version | Firmware version |
    +==============+=======================+==================+
-   |    20.11     |         2.13.10       |       8.00       |
+   |    21.02     |         2.14.13       |       8.00       |
+   +--------------+-----------------------+------------------+
+   |    20.11     |         2.14.13       |       8.00       |
    +--------------+-----------------------+------------------+
    |    20.08     |         2.12.6        |       7.30       |
    +--------------+-----------------------+------------------+
@@ -133,6 +148,8 @@ For X722,
    +--------------+-----------------------+------------------+
    | DPDK version | Kernel driver version | Firmware version |
    +==============+=======================+==================+
+   |    21.02     |         2.14.13       |       5.00       |
+   +--------------+-----------------------+------------------+
    |    20.11     |         2.13.10       |       5.00       |
    +--------------+-----------------------+------------------+
    |    20.08     |         2.12.6        |       4.11       |
@@ -209,15 +226,6 @@ Runtime Config Options
   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
@@ -732,6 +740,11 @@ When programming cloud filters for IPv4/6_UDP/TCP/SCTP with SRC port only or DST
 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
 ----------------------------------------------