[dpdk-stable] patch 'doc: fix mark action zero value in mlx5 guide' has been queued to stable release 20.11.1

[luca.boccassi at gmail.com]

Hi,

FYI, your patch has been queued to stable release 20.11.1

Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet.
It will be pushed if I get no objections before 02/14/21. So please
shout if anyone has objections.

Also note that after the patch there's a diff of the upstream commit vs the
patch applied to the branch. This will indicate if there was any rebasing
needed to apply to the stable branch. If there were code changes for rebasing
(ie: not only metadata diffs), please double check that the rebase was
correctly done.

Queued patches are on a temporary branch at:
https://github.com/bluca/dpdk-stable

This queued commit can be viewed at:
https://github.com/bluca/dpdk-stable/commit/f3bf966edc393ada2b7c1eb621e9452598d5240f

Thanks.

Luca Boccassi

---
>From f3bf966edc393ada2b7c1eb621e9452598d5240f Mon Sep 17 00:00:00 2001
From: Viacheslav Ovsiienko <viacheslavo at nvidia.com>
Date: Fri, 5 Feb 2021 14:15:04 +0200
Subject: [PATCH] doc: fix mark action zero value in mlx5 guide

[ upstream commit b8ee0a16cb844027495968941a101f37964073cc ]

The zero value in flow MARK action is reported in Rx datapath
as tagged with zero FDIR ID. Once packet is marked in flow engine
it will be always reported as tagged. For metadata only the zero
value means there is "no metadata" in the packet and the metadata
flag is not set for the case.

Fixes: 3ceeed9f7855 ("doc: update flow mark action in mlx5 guide")

Signed-off-by: Viacheslav Ovsiienko <viacheslavo at nvidia.com>
---
 doc/guides/nics/mlx5.rst | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 715c5b5be7..24d5a69227 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -823,8 +823,10 @@ Driver options
   of the extensive metadata features. The legacy Verbs supports FLAG and
   MARK metadata actions over NIC Rx steering domain only.
 
-  The setting MARK or META value to zero means there is no item provided and
-  receiving datapath will not report in mbufs these items are present.
+  Setting META value to zero in flow action means there is no item provided
+  and receiving datapath will not report in mbufs the metadata are present.
+  Setting MARK value to zero in flow action means the zero FDIR ID value
+  will be reported on packet receiving.
 
   For the MARK action the last 16 values in the full range are reserved for
   internal PMD purposes (to emulate FLAG action). The valid range for the
-- 
2.29.2

---
  Diff of the applied patch vs upstream commit (please double-check if non-empty:
---
--- -	2021-02-12 23:40:10.017503101 +0000
+++ 0004-doc-fix-mark-action-zero-value-in-mlx5-guide.patch	2021-02-12 23:40:09.879090655 +0000
@@ -1 +1 @@
-From b8ee0a16cb844027495968941a101f37964073cc Mon Sep 17 00:00:00 2001
+From f3bf966edc393ada2b7c1eb621e9452598d5240f Mon Sep 17 00:00:00 2001
@@ -5,0 +6,2 @@
+[ upstream commit b8ee0a16cb844027495968941a101f37964073cc ]
+
@@ -13 +14,0 @@
-Cc: stable at dpdk.org
@@ -21 +22 @@
-index 51d81a0206..ff5c8c15d9 100644
+index 715c5b5be7..24d5a69227 100644
@@ -24 +25 @@
-@@ -875,8 +875,10 @@ Driver options
+@@ -823,8 +823,10 @@ Driver options