From: Stephen Hemminger <stephen@networkplumber.org>
To: beilei.xing@intel.com
Cc: jingjing.wu@intel.com, dev@dpdk.org
Subject: Re: [PATCH] doc: update doc for idpf and cpfl
Date: Wed, 19 Jul 2023 09:15:22 -0700 [thread overview]
Message-ID: <20230719091522.1e3e3ed3@hermes.local> (raw)
In-Reply-To: <20230718170212.993131-1-beilei.xing@intel.com>
On Tue, 18 Jul 2023 17:02:12 +0000
beilei.xing@intel.com wrote:
> 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>
> ---
> doc/guides/nics/cpfl.rst | 16 ++++++++++++++++
> doc/guides/nics/idpf.rst | 16 ++++++++++++++++
> 2 files changed, 32 insertions(+)
>
> diff --git a/doc/guides/nics/cpfl.rst b/doc/guides/nics/cpfl.rst
> index e88008e16e..258e89ed48 100644
> --- a/doc/guides/nics/cpfl.rst
> +++ b/doc/guides/nics/cpfl.rst
> @@ -21,6 +21,22 @@ 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.03 | 0.6.0 |
> + +------------+------------------+
> + | 23.07 | 0.9.1 |
> + +------------+------------------+
>
Since 23.03 is not an LTS release, it will not be supported when 23.07
is release. Probably best not to clutter up docs with 23.03
next prev parent reply other threads:[~2023-07-19 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 17:02 beilei.xing
2023-07-19 16:15 ` Stephen Hemminger [this message]
2023-07-25 6:57 ` Xing, Beilei
2023-07-25 15:25 ` [PATCH v2] " beilei.xing
2023-07-27 21:04 ` 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=20230719091522.1e3e3ed3@hermes.local \
--to=stephen@networkplumber.org \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
/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).