DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Qi Zhang <qi.z.zhang@intel.com>,
	john.mcnamara@intel.com, paul.m.stillwell.jr@intel.com
Cc: helin.zhang@intel.com, xiaolong.ye@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: add matching list for ice
Date: Mon, 18 Nov 2019 17:31:02 +0000	[thread overview]
Message-ID: <585864a2-4e67-f32c-2559-9eafa25e16bc@intel.com> (raw)
In-Reply-To: <20191118040334.36456-1-qi.z.zhang@intel.com>

On 11/18/2019 4:03 AM, Qi Zhang wrote:
> Add kernel driver, firmware and DDP package matching list
> for ice PMD.
> 
> Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
> ---
>  doc/guides/nics/ice.rst | 18 ++++++++++++++++++
>  1 file changed, 18 insertions(+)
> 
> diff --git a/doc/guides/nics/ice.rst b/doc/guides/nics/ice.rst
> index 1a426438d..7ff33d7f0 100644
> --- a/doc/guides/nics/ice.rst
> +++ b/doc/guides/nics/ice.rst
> @@ -20,6 +20,24 @@ Prerequisites
>  - To get better performance on Intel platforms, please follow the "How to get best performance with NICs on Intel platforms"
>    section of the :ref:`Getting Started Guide for Linux <linux_gsg>`.
>  
> +Recommended Matching List
> +-------------------------
> +
> +It is highly recommended to upgrade the ice kernel driver and firmware and
> +DDP packages to avoid the compatibility issues with ice PMD. Here is the
> +suggested matching list.
> +
> +   +-----------------+-----------------------+------------------+----------------+-------------------+
> +   | DPDK version    | Kernel driver version | Firmware version | DDP OS Package | DDP COMMS Package |
> +   +=================+=======================+==================+================+===================+
> +   |      19.11      |        0.12.25        |     1.1.16.39    |      1.3.4     |       1.3.10      |
> +   +-----------------+-----------------------+------------------+----------------+-------------------+
> +   |      19.08      |        0.10.1         |     1.1.12.7     |      1.2.0     |        N/A        |
> +   | (experimental)  |                       |                  |                |                   |
> +   +-----------------+-----------------------+------------------+----------------+-------------------+
> +   |      19.05      |        0.9.4          |     1.1.10.16    |      1.1.0     |        N/A        |
> +   | (experimental)  |                       |                  |                |                   |
> +   +-----------------+-----------------------+------------------+----------------+-------------------+
>  
>  Pre-Installation Configuration
>  ------------------------------
> 

I am getting following warnings [1] from doc build, can you please check?

[1]
.../doc/guides/nics/ice.rst:37: WARNING: Block quote ends without a blank line;
unexpected unindent.
.../doc/guides/nics/ice.rst:40: WARNING: Block quote ends without a blank line;
unexpected unindent.

      parent reply	other threads:[~2019-11-18 17:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-18  4:03 Qi Zhang
2019-11-18  5:32 ` Ye Xiaolong
2019-11-18 17:31 ` Ferruh Yigit [this message]

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=585864a2-4e67-f32c-2559-9eafa25e16bc@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=helin.zhang@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=paul.m.stillwell.jr@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=xiaolong.ye@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).