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 2FFDF4576A; Thu, 8 Aug 2024 13:27:21 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id AEC4A42798; Thu, 8 Aug 2024 13:27:20 +0200 (CEST) Received: from fout6-smtp.messagingengine.com (fout6-smtp.messagingengine.com [103.168.172.149]) by mails.dpdk.org (Postfix) with ESMTP id E914D40EDD for ; Thu, 8 Aug 2024 13:27:18 +0200 (CEST) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailfout.nyi.internal (Postfix) with ESMTP id 8BF5A138FCD6; Thu, 8 Aug 2024 07:27:18 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Thu, 08 Aug 2024 07:27:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1723116438; x=1723202838; bh=eqm131tnp+J3ACFGexkJgJyQD2ra/7HytF8Pudp974U=; b= kDPmtRgKseeHI4GNgnMc+f51kR9KRlNC68wsfW6e7CihVz5HPgDeBdh6ZaxyGjYk B63iv15RPGgLxHNDk+fTKfYlcayoKOJF0vcen84SLHEGhj/thQqCog/dQ9GkwKwP TOb3rV0Y/LOOgXpgDnd4VAW7Oez9CO/33bvxKf76L3Ni89TE9s+z74kEcGlDFqsw E6+jaB/Vp+CCm605M6H4UtooXDXa+s3dYC/T7vcE7c0jfBJZKPrslBeEJfUg330k QxByw73o0eXVC4OeL/CO390aQsFTes1efG/VRZBOQRWs5ALtSDmM/vXup8m++QcL Y9Hp45FTJvKfGQIxaPMv9g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1723116438; x= 1723202838; bh=eqm131tnp+J3ACFGexkJgJyQD2ra/7HytF8Pudp974U=; b=u E45a24bnY517nBzvYrYix8QOcXpM56wh+dQcsM770VRLM2XnipK9WlP12INYWxei G3RNxLgMeKOzqLrIrxrnS8tWLcV1ceevxHEEItIZiWZQrnr8Bq+cig4zCG9/vTYo 7t32w0aNtFXapM3m1jiqD6Vc5oJxNXVpInOLRLMa/NsOidArSCu7iIUMEZpvguQH 0yQSa/R+sVN6DsF75ngZw8zyJkQDHQnAL8Ps9RgqmFoF8CJavhAQIobrkyQro81/ /q0+RR4EDkh7+EH4JTCqg0zH+pHbNR19HnIfy8CehAsk96xIpK2irk91GJY5wFsK 3lbEXV5nXnoleQbnlETyw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrledvgdegtdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdpuffr tefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnth hsucdlqddutddtmdenucfjughrpefhvfevufffkfgjfhgggfgtsehtufertddttdejnecu hfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlh honhdrnhgvtheqnecuggftrfgrthhtvghrnhepjeduveehieevuddutdevfffgtdegkeeu veejffejgedtgeegkefgvdeugfefkeejnecuvehluhhsthgvrhfuihiivgeptdenucfrrg hrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvthdpnhgs pghrtghpthhtohepkedpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepsghinhhgii esnhhvihguihgrrdgtohhmpdhrtghpthhtoheprhgrshhlrghnugesnhhvihguihgrrdgt ohhmpdhrtghpthhtohepvhhirggthhgvshhlrghvohesnhhvihguihgrrdgtohhmpdhrtg hpthhtohepuggvvhesughpughkrdhorhhgpdhrtghpthhtohepohhrihhkrgesnhhvihgu ihgrrdgtohhmpdhrtghpthhtohepughsohhsnhhofihskhhisehnvhhiughirgdrtghomh dprhgtphhtthhopehsuhgrnhhmihhnghhmsehnvhhiughirgdrtghomhdprhgtphhtthho pehmrghtrghnsehnvhhiughirgdrtghomh X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 8 Aug 2024 07:27:17 -0400 (EDT) From: Thomas Monjalon To: Bing Zhao , Raslan Darawsheh Cc: Slava Ovsiienko , "dev@dpdk.org" , Ori Kam , Dariusz Sosnowski , Suanming Mou , Matan Azrad Subject: Re: [PATCH v2] net/mlx5: add metadata split for compatibility API Date: Thu, 08 Aug 2024 13:27:15 +0200 Message-ID: <3297286.oiGErgHkdL@thomas> In-Reply-To: References: <20240613125146.547992-1-bingz@nvidia.com> <20240704102603.3355-1-bingz@nvidia.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" 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 09/07/2024 11:36, Raslan Darawsheh: > Hi, > > From: Bing Zhao > Sent: Thursday, July 4, 2024 1:26 PM > To: Slava Ovsiienko; dev@dpdk.org; Raslan Darawsheh > Cc: Ori Kam; Dariusz Sosnowski; Suanming Mou; Matan Azrad > Subject: [PATCH v2] net/mlx5: add metadata split for compatibility API > > The method will not create any new flow rule implicitly during split > stage, but only generate needed items, actions and attributes based > on the detection. > > All the rules will still be created in the flow_hw_list_create(). > > In the meanwhile, once the mark action is specified in the FDB rule, > a new rule in the NIC Rx will be created to: > 1. match the mark value on REG_C_x in FDB and set it into Rx > flow tag field. > 2. copy the metadata in REG_C_x' into the REG_B. > > If there is no mark, the default rule with only copying metadata > will be hit if there is Queue or RSS action in the NIC Rx rule. > > Regarding the NIC Tx, only the metadata is relevant and it will be > copied in NIC Tx from REG_A into some REG_C_x. The current HWS > implementation already has already supported in the default copy > rule or the default SQ miss rule in the NIC Tx root table. > > Signed-off-by: Bing Zhao > Acked-by: Dariusz Sosnowski > > Patch applied to next-net-mlx, It looks like this patch was missed, probably not pushed in the branch. Please send a v3 for integration in 24.11.