DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@mellanox.com>
To: Dekel Peled <dekelp@mellanox.com>,
	Matan Azrad <matan@mellanox.com>,
	Shahaf Shuler <shahafs@mellanox.com>,
	Slava Ovsiienko <viacheslavo@mellanox.com>,
	"john.mcnamara@intel.com" <john.mcnamara@intel.com>,
	"marko.kovacevic@intel.com" <marko.kovacevic@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: update mlx5 firmware configuration	guidelines
Date: Wed, 25 Mar 2020 14:24:09 +0000	[thread overview]
Message-ID: <AM0PR05MB67077FB3C40A33DCFC5752BBC2CE0@AM0PR05MB6707.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <8a85deaa18a873708781ef212697abd07a10f9c3.1585045420.git.dekelp@mellanox.com>

Hi,

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Dekel Peled
> Sent: Tuesday, March 24, 2020 1:31 PM
> To: Matan Azrad <matan@mellanox.com>; Shahaf Shuler
> <shahafs@mellanox.com>; Slava Ovsiienko <viacheslavo@mellanox.com>;
> john.mcnamara@intel.com; marko.kovacevic@intel.com
> Cc: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] doc: update mlx5 firmware configuration
> guidelines
> 
> This patch updates the MLX5 PMD documentations, adding Flex parser
> settings and correcting minimal versions numbers.
> 
> Signed-off-by: Dekel Peled <dekelp@mellanox.com>
> ---
>  doc/guides/nics/mlx5.rst | 14 +++++++++++---
>  1 file changed, 11 insertions(+), 3 deletions(-)
> 
> diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
> index afd11cd..e8f9984 100644
> --- a/doc/guides/nics/mlx5.rst
> +++ b/doc/guides/nics/mlx5.rst
> @@ -822,6 +822,12 @@ Below are some firmware configurations listed.
>      IP_OVER_VXLAN_EN=1
>      IP_OVER_VXLAN_PORT=<udp dport>
> 
> +- enable VXLAN-GPE tunnel flow matching::
> +
> +    FLEX_PARSER_PROFILE_ENABLE=0
> +    or
> +    FLEX_PARSER_PROFILE_ENABLE=2
> +
>  - enable IP-in-IP tunnel flow matching::
> 
>      FLEX_PARSER_PROFILE_ENABLE=0
> @@ -837,6 +843,8 @@ Below are some firmware configurations listed.
>  - enable Geneve flow matching::
> 
>     FLEX_PARSER_PROFILE_ENABLE=0
> +   or
> +   FLEX_PARSER_PROFILE_ENABLE=1
> 
>  - enable GTP flow matching::
> 
> @@ -933,15 +941,15 @@ thanks to these environment variables:
>  Mellanox OFED/EN
>  ^^^^^^^^^^^^^^^^
> 
> -- Mellanox OFED version: ** 4.5, 4.6** /
> -  Mellanox EN version: **4.5, 4.6**
> +- Mellanox OFED version: **4.5** and above /
> +  Mellanox EN version: **4.5** and above
>  - firmware version:
> 
>    - ConnectX-4: **12.21.1000** and above.
>    - ConnectX-4 Lx: **14.21.1000** and above.
>    - ConnectX-5: **16.21.1000** and above.
>    - ConnectX-5 Ex: **16.21.1000** and above.
> -  - ConnectX-6: **20.99.5374** and above.
> +  - ConnectX-6: **20.27.0090** and above.
>    - ConnectX-6 Dx: **22.27.0090** and above.
>    - BlueField: **18.25.1010** and above.
> 
> --
> 1.8.3.1

Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      parent reply	other threads:[~2020-03-25 14:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-24 11:31 Dekel Peled
2020-03-24 15:59 ` Matan Azrad
2020-03-25 14:24 ` Raslan Darawsheh [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=AM0PR05MB67077FB3C40A33DCFC5752BBC2CE0@AM0PR05MB6707.eurprd05.prod.outlook.com \
    --to=rasland@mellanox.com \
    --cc=dekelp@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=matan@mellanox.com \
    --cc=shahafs@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).