From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 5A5EAA0C50; Sun, 1 Aug 2021 12:22:40 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 46444410F3; Sun, 1 Aug 2021 12:22:40 +0200 (CEST) Received: from shelob.oktetlabs.ru (shelob.oktetlabs.ru [91.220.146.113]) by mails.dpdk.org (Postfix) with ESMTP id 1C30A410EE for ; Sun, 1 Aug 2021 12:22:39 +0200 (CEST) Received: by shelob.oktetlabs.ru (Postfix, from userid 122) id D91E97F6C4; Sun, 1 Aug 2021 13:22:38 +0300 (MSK) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shelob.oktetlabs.ru X-Spam-Level: X-Spam-Status: No, score=0.8 required=5.0 tests=ALL_TRUSTED, DKIM_ADSP_DISCARD, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.2 Received: from aros.oktetlabs.ru (aros.oktetlabs.ru [192.168.38.17]) by shelob.oktetlabs.ru (Postfix) with ESMTP id 1BB017F567; Sun, 1 Aug 2021 13:22:28 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 shelob.oktetlabs.ru 1BB017F567 Authentication-Results: shelob.oktetlabs.ru/1BB017F567; dkim=none; dkim-atps=neutral From: Andrew Rybchenko To: Thomas Monjalon , Ferruh Yigit , Ori Kam Cc: dev@dpdk.org, Eli Britstein , Ilya Maximets , Ajit Khaparde , Matan Azrad , Ivan Malov , Viacheslav Galaktionov Date: Sun, 1 Aug 2021 13:22:14 +0300 Message-Id: <20210801102214.1566104-2-andrew.rybchenko@oktetlabs.ru> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20210801102214.1566104-1-andrew.rybchenko@oktetlabs.ru> References: <20210801102214.1566104-1-andrew.rybchenko@oktetlabs.ru> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-dev] [PATCH 2/2] ethdev: announce clarification of implicit filter by port X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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 --- 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 6e6413c89f..4d174c8952 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -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. -- 2.30.2