* [dpdk-stable] [PATCH v2] doc: add VLAN flow limitation on mlx5 PMD
[not found] <20170606142016.140162-1-shahafs@mellanox.com>
@ 2017-06-13 10:20 ` Shahaf Shuler
2017-06-15 13:44 ` Ferruh Yigit
0 siblings, 1 reply; 2+ messages in thread
From: Shahaf Shuler @ 2017-06-13 10:20 UTC (permalink / raw)
To: john.mcnamara; +Cc: nelio.laranjeiro, adrien.mazarguil, dev, stable
On mlx5 PMD Flow pattern without any specific vlan will match for vlan
packets as well.
Cc: stable@dpdk.org
Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
Acked-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
---
on v2:
* move the reported issue to mlx5 guide as it is present since commit
12475fb203ad ("net/mlx5: support VLAN flow item")
---
doc/guides/nics/mlx5.rst | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index da6dc278e..a68b7adc0 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -330,6 +330,26 @@ Supported NICs
* Mellanox(R) ConnectX(R)-5 100G MCX556A-ECAT (2x100G)
* Mellanox(R) ConnectX(R)-5 Ex EN 100G MCX516A-CDAT (2x100G)
+Known issues
+------------
+
+* **Flow pattern without any specific vlan will match for vlan packets as well.**
+
+ When VLAN spec is not specified in the pattern, the matching rule will be created with VLAN as a wild card.
+ Meaning, the flow rule::
+
+ flow create 0 ingress pattern eth / vlan vid is 3 / ipv4 / end ...
+
+ Will only match vlan packets with vid=3. and the flow rules::
+
+ flow create 0 ingress pattern eth / ipv4 / end ...
+
+ Or::
+
+ flow create 0 ingress pattern eth / vlan / ipv4 / end ...
+
+ Will match any ipv4 packet (VLAN included).
+
Notes for testpmd
-----------------
--
2.12.0
^ permalink raw reply [flat|nested] 2+ messages in thread