[2/2] ethdev: announce clarification of implicit filter by port
Checks
Commit Message
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 criterias.
These aspects should be documented and drivers and applications
which misuse it must be fixed.
Signed-off-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
---
doc/guides/rel_notes/deprecation.rst | 5 +++++
1 file changed, 5 insertions(+)
Comments
Hi Andrew,
Acked-by: Ori Kam <orika@nvidia.com>
Best,
Ori
> -----Original Message-----
> From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
> Sent: Sunday, August 1, 2021 1:22 PM
@@ -163,3 +163,8 @@ Deprecation Notices
clarification. Structure rte_flow_action_port_id will be extended to
specify traffic direction to 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.