From 80ab563ba9704101324189526634330d71db0484 Mon Sep 17 00:00:00 2001 From: Andrew Rybchenko Date: Mon, 2 Aug 2021 22:57:23 +0300 Subject: [PATCH] doc: announce clarification of implicit filter by port Transfer flow rules may be applied to traffic entering switch from many sources. There are flow API pattern items which allow to specify ingress port match criteria explicitly, but it is not documented if ethdev port used to create flow rule adds any implicit match criteria and how it coexists with explicit ones. These aspects should be documented and drivers and applications which use it in a different way must be fixed. Signed-off-by: Andrew Rybchenko Acked-by: Ori Kam Acked-by: Ajit Khaparde Acked-by: Thomas Monjalon --- doc/guides/rel_notes/deprecation.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index 4799b642a7..26051cc589 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -134,6 +134,11 @@ Deprecation Notices traffic direction to the represented entity or ethdev port itself in DPDK 21.11. +* ethdev: Flow API documentation is unclear if ethdev port used to create + a flow rule adds any implicit match criteria in the case of transfer rules. + The semantics will be clarified in DPDK 21.11 and it will require fixes in + drivers and applications which interpret it in a different way. + * ethdev: The flow API matching pattern structures, ``struct rte_flow_item_*``, should start with relevant protocol header. Some matching pattern structures implements this by duplicating protocol header -- 2.20.1