From: beilei.xing@intel.com
To: jingjing.wu@intel.com, stephen@networkplumber.org
Cc: dev@dpdk.org, Beilei Xing <beilei.xing@intel.com>
Subject: [PATCH v2] doc: update doc for idpf and cpfl
Date: Tue, 25 Jul 2023 15:25:03 +0000 [thread overview]
Message-ID: <20230725152503.5814-1-beilei.xing@intel.com> (raw)
In-Reply-To: <20230718170212.993131-1-beilei.xing@intel.com>
From: Beilei Xing <beilei.xing@intel.com>
Add recommended matching list for idpf pmd and cpfl pmd.
Signed-off-by: Beilei Xing <beilei.xing@intel.com>
---
v2 change:
- Remove description about 23.03
doc/guides/nics/cpfl.rst | 14 ++++++++++++++
doc/guides/nics/idpf.rst | 14 ++++++++++++++
2 files changed, 28 insertions(+)
diff --git a/doc/guides/nics/cpfl.rst b/doc/guides/nics/cpfl.rst
index e88008e16e..06a18694b4 100644
--- a/doc/guides/nics/cpfl.rst
+++ b/doc/guides/nics/cpfl.rst
@@ -21,6 +21,20 @@ To get better performance on Intel platforms,
please follow the :doc:`../linux_gsg/nic_perf_intel_platform`.
+Recommended Matching List
+-------------------------
+
+It is highly recommended to upgrade the MEV-ts release to avoid the compatibility issues
+with the cpfl PMD.
+Here is the suggested matching list which has been tested and verified.
+
+ +------------+------------------+
+ | DPDK | MEV-ts release |
+ +============+==================+
+ | 23.07 | 0.9.1 |
+ +------------+------------------+
+
+
Configuration
-------------
diff --git a/doc/guides/nics/idpf.rst b/doc/guides/nics/idpf.rst
index 3693d82255..89351f1a22 100644
--- a/doc/guides/nics/idpf.rst
+++ b/doc/guides/nics/idpf.rst
@@ -19,6 +19,20 @@ To get better performance on Intel platforms,
please follow the :doc:`../linux_gsg/nic_perf_intel_platform`.
+Recommended Matching List
+-------------------------
+
+It is highly recommended to upgrade the idpf kernel driver, MEV-ts release to avoid
+the compatibility issues with the idpf PMD.
+Here is the suggested matching list which has been tested and verified.
+
+ +------------+---------------+------------------+
+ | DPDK | Kernel Driver | MEV-ts release |
+ +============+===============+==================+
+ | 23.07 | 0.0.710 | 0.9.1 |
+ +------------+---------------+------------------+
+
+
Configuration
-------------
--
2.34.1
next prev parent reply other threads:[~2023-07-25 7:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 17:02 [PATCH] " beilei.xing
2023-07-19 16:15 ` Stephen Hemminger
2023-07-25 6:57 ` Xing, Beilei
2023-07-25 15:25 ` beilei.xing [this message]
2023-07-27 21:04 ` [PATCH v2] " Thomas Monjalon
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=20230725152503.5814-1-beilei.xing@intel.com \
--to=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=stephen@networkplumber.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).