DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Qiming Yang <qiming.yang@intel.com>,
	dev@dpdk.org, qi.z.zhang@intel.com, "Zhang,
	Yuying" <yuying.zhang@intel.com>,
	"Xing, Beilei" <beilei.xing@intel.com>,
	"Wu, Wenjun1" <wenjun1.wu@intel.com>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>,
	"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [PATCH v2] doc: update matching list for i40e and ice driver
Date: Fri, 10 Nov 2023 12:20:55 +0000	[thread overview]
Message-ID: <180b634f-94fe-f7f8-92ec-b651653560ea@redhat.com> (raw)
In-Reply-To: <d212cb6e-53fd-b017-0d93-ff0b014768c4@redhat.com>

On 01/11/2023 11:42, Kevin Traynor wrote:
> On 11/11/2022 05:27, Qiming Yang wrote:
>> Add recommended matching list for ice PMD in DPDK 22.07 and
>> i40e PMD in DPDK 22.07 and 22.11.
>>
>> Signed-off-by: Qiming Yang <qiming.yang@intel.com>
>> ---
>>    doc/guides/nics/i40e.rst | 8 ++++++++
>>    doc/guides/nics/ice.rst  | 2 ++
>>    2 files changed, 10 insertions(+)
>>
>> diff --git a/doc/guides/nics/i40e.rst b/doc/guides/nics/i40e.rst
>> index a0992dbc6c..a6c7dbd080 100644
>> --- a/doc/guides/nics/i40e.rst
>> +++ b/doc/guides/nics/i40e.rst
>> @@ -101,6 +101,10 @@ For X710/XL710/XXV710,
>>       +--------------+-----------------------+------------------+
>>       | DPDK version | Kernel driver version | Firmware version |
>>       +==============+=======================+==================+
>> +   |    22.11     |         2.20.12       |       9.01       |
>> +   +--------------+-----------------------+------------------+
>> +   |    22.07     |         2.19.3        |       8.70       |
>> +   +--------------+-----------------------+------------------+
>>       |    22.03     |         2.17.15       |       8.30       |
>>       +--------------+-----------------------+------------------+
>>       |    21.11     |         2.17.4        |       8.30       |
>> @@ -156,6 +160,10 @@ For X722,
>>       +--------------+-----------------------+------------------+
>>       | DPDK version | Kernel driver version | Firmware version |
>>       +==============+=======================+==================+
>> +   |    22.11     |         2.20.12       |       6.00       |
>> +   +--------------+-----------------------+------------------+
>> +   |    22.07     |         2.19.3        |       5.60       |
>> +   +--------------+-----------------------+------------------+
>>       |    22.03     |         2.17.15       |       5.50       |
>>       +--------------+-----------------------+------------------+
>>       |    21.11     |         2.17.4        |       5.30       |
> 
> 
> The text above the table says:
> 
> "It is highly recommended to upgrade the i40e kernel driver and firmware
> to avoid the compatibility issues with i40e PMD. Here is the suggested
> matching list which has been tested and verified. The detailed
> information can refer to chapter Tested Platforms/Tested NICs in release
> notes."
> 
> The table is only showing the out-of-tree Kernel driver versions. The
> tested section shows that in-tree Kernel drivers are tested with as well.
> 
> The issue is that this section says "Here is the suggested matching
> list" and only lists out-of-tree drivers.
> 
> It is probably just a left over from when in-tree drivers had version
> numbers but it is causing some confusion for users as it implies that
> the Intel recommendation is to use out-of-tree drivers and not in-tree.
> 
> So I suggest that another column is added here to also show the in-tree
> kernel driver tested with.
> 
> What do you think ?
> 

Any thoughts on this ?

It would be best to list both, but it might be too much when in-tree 
drivers are being tested on multiple kernels etc.

Removing the column could work, but may lose some info for older releases.

So I just sent a patch to update the text:
http://inbox.dpdk.org/dev/20231110121407.444282-1-ktraynor@redhat.com

>> diff --git a/doc/guides/nics/ice.rst b/doc/guides/nics/ice.rst
>> index c7f82c261d..ce075e067c 100644
>> --- a/doc/guides/nics/ice.rst
>> +++ b/doc/guides/nics/ice.rst
>> @@ -64,6 +64,8 @@ The detailed information can refer to chapter Tested Platforms/Tested NICs in re
>>       +-----------+---------------+-----------------+-----------+--------------+-----------+
>>       |    22.03  |     1.8.3     |      1.3.28     |  1.3.35   |    1.3.8     |    3.2    |
>>       +-----------+---------------+-----------------+-----------+--------------+-----------+
>> +   |    22.07  |     1.9.11    |      1.3.30     |  1.3.37   |    1.3.10    |    4.0    |
>> +   +-----------+---------------+-----------------+-----------+--------------+-----------+
>>    
>>    Pre-Installation Configuration
>>    ------------------------------
> 


      reply	other threads:[~2023-11-10 12:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09  1:46 [PATCH] " Qiming Yang
2022-11-10  3:27 ` Yang, Qiming
2022-11-11  5:27 ` [PATCH v2] " Qiming Yang
2022-11-11  9:09   ` Zhang, Qi Z
2023-11-01 11:42   ` Kevin Traynor
2023-11-10 12:20     ` Kevin Traynor [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=180b634f-94fe-f7f8-92ec-b651653560ea@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=techboard@dpdk.org \
    --cc=wenjun1.wu@intel.com \
    --cc=yuying.zhang@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).