From: Qiming Yang <qiming.yang@intel.com>
To: dev@dpdk.org
Cc: qi.z.zhang@intel.com, Qiming Yang <qiming.yang@intel.com>,
stable@dpdk.org
Subject: [PATCH v4] doc: update matching versions in i40e guide
Date: Fri, 20 May 2022 15:04:41 +0800 [thread overview]
Message-ID: <20220520070441.72840-1-qiming.yang@intel.com> (raw)
In-Reply-To: <20220426054706.53091-1-qiming.yang@intel.com>
Add recommended matching list for i40e PMD in DPDK 21.05,
21.08, 21.11 and 22.03. And add a known issue when FW upgrade
to a version higher than 8.4.
Cc: stable@dpdk.org
Signed-off-by: Qiming Yang <qiming.yang@intel.com>
---
v2:
* added known issue in FW 8.4+
v3:
* updated x722 FW version
v4:
* minor express change
---
doc/guides/nics/i40e.rst | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/doc/guides/nics/i40e.rst b/doc/guides/nics/i40e.rst
index ef91b3a1ac..aedb1afc4b 100644
--- a/doc/guides/nics/i40e.rst
+++ b/doc/guides/nics/i40e.rst
@@ -101,6 +101,14 @@ For X710/XL710/XXV710,
+--------------+-----------------------+------------------+
| DPDK version | Kernel driver version | Firmware version |
+==============+=======================+==================+
+ | 22.03 | 2.17.15 | 8.30 |
+ +--------------+-----------------------+------------------+
+ | 21.11 | 2.17.4 | 8.30 |
+ +--------------+-----------------------+------------------+
+ | 21.08 | 2.15.9 | 8.30 |
+ +--------------+-----------------------+------------------+
+ | 21.05 | 2.15.9 | 8.30 |
+ +--------------+-----------------------+------------------+
| 21.02 | 2.14.13 | 8.00 |
+--------------+-----------------------+------------------+
| 20.11 | 2.14.13 | 8.00 |
@@ -148,6 +156,14 @@ For X722,
+--------------+-----------------------+------------------+
| DPDK version | Kernel driver version | Firmware version |
+==============+=======================+==================+
+ | 22.03 | 2.17.15 | 5.50 |
+ +--------------+-----------------------+------------------+
+ | 21.11 | 2.17.4 | 5.30 |
+ +--------------+-----------------------+------------------+
+ | 21.08 | 2.15.9 | 5.30 |
+ +--------------+-----------------------+------------------+
+ | 21.05 | 2.15.9 | 5.30 |
+ +--------------+-----------------------+------------------+
| 21.02 | 2.14.13 | 5.00 |
+--------------+-----------------------+------------------+
| 20.11 | 2.13.10 | 5.00 |
@@ -771,6 +787,13 @@ it will fail and return the info "Conflict with the first rule's input set",
which means the current rule's input set conflicts with the first rule's.
Remove the first rule if want to change the input set of the PCTYPE.
+PF reset fail after QinQ set with FW >= 8.4
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+If upgrade FW to version 8.4 and higher, after set MAC VLAN filter and configure outer VLAN on PF, kill
+DPDK process will cause the card crash.
+
+
Example of getting best performance with l3fwd example
------------------------------------------------------
--
2.17.1
next prev parent reply other threads:[~2022-05-20 7:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 5:47 [PATCH] " Qiming Yang
2022-05-09 7:18 ` [PATCH v2] " Qiming Yang
2022-05-16 5:55 ` [PATCH v3] " Qiming Yang
2022-05-16 10:29 ` Kevin Traynor
2022-05-20 2:30 ` Yang, Qiming
2022-05-20 7:04 ` Qiming Yang [this message]
2022-05-21 2:22 ` [PATCH v4] " Zhang, Qi Z
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220520070441.72840-1-qiming.yang@intel.com \
--to=qiming.yang@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=stable@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).