DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Cc: dev@dpdk.org, rasland@mellanox.com
Subject: Re: [dpdk-dev] [PATCH] doc: fix the release notes for Mellanox PMD
Date: Thu, 06 Aug 2020 17:53:27 +0200	[thread overview]
Message-ID: <6036226.GaFkFv8pJ2@thomas> (raw)
In-Reply-To: <1596728949-8869-1-git-send-email-viacheslavo@mellanox.com>

06/08/2020 17:49, Viacheslav Ovsiienko:
> The mlx5 PMD might not work on Power 9 platform with OFED
> version 5.1-0.6.6.0 (latest GA release at the moment).
> Release notes know issues chapter is updated accordingly,
> workaround is proposed.
> 
> Fixes: 544f35c334e5 ("doc: add tested platforms with Mellanox NICs")
> 
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> ---
>  doc/guides/rel_notes/release_20_08.rst | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/doc/guides/rel_notes/release_20_08.rst b/doc/guides/rel_notes/release_20_08.rst
> index 9761f5a..147a380 100644
> --- a/doc/guides/rel_notes/release_20_08.rst
> +++ b/doc/guides/rel_notes/release_20_08.rst
> @@ -331,6 +331,11 @@ Known Issues
>     Also, make sure to start the actual text at the margin.

Please see above. Indent is wrong.

>     =========================================================
>  
> +   * **mlx5 PMD might not work on Power 9 with OFED 5.1-0.6.6.0.**

Just to confirm, "might" means it works sometimes.
Matter of luck?

> +
> +     Consider using the newer OFED releases, the previous
> +     OFED 5.0-2.1.8.0, or upstream rdma-core library v29 and above.
> +
>  
>  Tested Platforms
>  ----------------
> @@ -489,4 +494,4 @@ Tested Platforms
>  
>    * OFED:
>  
> -    * MLNX_OFED 5.1-0.6.6.0
> +    * MLNX_OFED 5.0-2.1.8.0




      reply	other threads:[~2020-08-06 15:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 15:49 Viacheslav Ovsiienko
2020-08-06 15:53 ` Thomas Monjalon [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=6036226.GaFkFv8pJ2@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=rasland@mellanox.com \
    --cc=viacheslavo@mellanox.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).