From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id BE328A09E1 for ; Fri, 13 Nov 2020 20:22:11 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 8DA17C8BC; Fri, 13 Nov 2020 20:22:10 +0100 (CET) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 32988C876; Fri, 13 Nov 2020 20:22:05 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id CA70D5C0039; Fri, 13 Nov 2020 14:22:03 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Fri, 13 Nov 2020 14:22:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm2; bh= EvU3eJj8nJUN2ddHtZerAM2JNlTJcWir0BqSPARp1QA=; b=nazEAqk1M9vjAxas 45yozkTnWE1g18McMoL2nQdFeyjF2j3qFIZ20FiWzpZFIhSe3faggdE8MpEd+QT+ xLoewts4pLApwGKgpiICXQ9ZkqFqc2E+4SnJsBNDgMeQQr7DlruS++7pYCsuGvwo BSR3W83BSLvTCThD2+8tiPm6EjpkvtH+MTNH8jNRUt/0DpibBO6CrQ09YcoTVX9I etEyK8Vy9+BZR/cduOHFZ7Nv0g/OrPwbAdkj+3FeA7dwh7QIV4iYD8/T/71iqbmA WDGO+GC2w2/HN6gkTFT9IzVZo6CWQNjhZT+9yjHfqU15n3xDrpIgsC5ZwRv0vIIp rnUnYA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=EvU3eJj8nJUN2ddHtZerAM2JNlTJcWir0BqSPARp1 QA=; b=DX1+PvngxfX6ZAEhIHhgTdubmzYs4BNJXBn5XJ8SS67rwVkXQPyzb0ShG fY0OAcqEstHLkExpM2iJpa+GYhnUMvVUmWl61qrOulvdP5v1REApEwIa5WrEhO7e BbrDr65mlGgzsG+bQ0Tj7cSwkkCYIdylOH0nnP4R2ZVrIWOgqISBH77t7RS8mxz4 5IIHO0JpIMM1AyCYzJNAQNT9dS0wjilsFooKDO8xi77QU9ZxYDfiSnWFYPrpDROR gLIRXMeO9GgKrjUouKqJVk1k9yv6QFNMlnBOWzYBoO6LG/14c4XlGwZNQsVB3AOJ HShC5EczIx8VqtdppLC8tZS0n9HAw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedruddvhedguddvgecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedugefgvdefudfftdefgeelgffhueekgfffhfeujedtteeutdej ueeiiedvffegheenucfkphepjeejrddufeegrddvtdefrddukeegnecuvehluhhsthgvrh fuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgr lhhonhdrnhgvth X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 5658F3064AA7; Fri, 13 Nov 2020 14:22:02 -0500 (EST) From: Thomas Monjalon To: "Xueming(Steven) Li" Cc: Slava Ovsiienko , dev@dpdk.org, Asaf Penso , "bingz@mellanox.com" , "stable@dpdk.org" , Matan Azrad Date: Fri, 13 Nov 2020 20:22:01 +0100 Message-ID: <2780604.77yy3yqIK2@thomas> In-Reply-To: References: <1604962679-20351-1-git-send-email-xuemingl@nvidia.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] net/mlx5: fix nested flow creation error X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" > > If xmedata mode 1 enabled and create a flow with RSS and mark action, there > > was an error that rdma-core failed to create RQT due to wrong queue > > definition. This was due to mixed flow creation in thread specific flow > > workspace. > > > > This patch introduces nested flow workspace(context data), each flow uses > > dedicate flow workspace, pop and restore workspace when nested flow > > creation done, the original flow with continue with original flow workspace. > > The total number of thread specific flow workspace should be > > 2 due to only one nested flow creation scenario so far. > > > > Fixes: 8bb81f2649b1 ("net/mlx5: use thread specific flow workspace") > > Fixes: 3ac3d8234b82 ("net/mlx5: fix index when creating flow") > > Cc: bingz@mellanox.com > > Cc: stable@dpdk.org > > > > Signed-off-by: Xueming Li > Acked-by: Matan Azrad Applied in next-net-mlx, thanks.