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 98BDFA04E6; Tue, 17 Nov 2020 15:13:01 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id B69E137B0; Tue, 17 Nov 2020 15:12:59 +0100 (CET) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id D1903F90 for ; Tue, 17 Nov 2020 15:12:56 +0100 (CET) IronPort-SDR: cWrDpSxtJWhw9ie96tVt4Og7wj/3meuZuohfUxh3fpcpP/WRLMmAjCto/JUrKObuQ55A8m1T02 SyE3tSs4dUHw== X-IronPort-AV: E=McAfee;i="6000,8403,9807"; a="157958464" X-IronPort-AV: E=Sophos;i="5.77,485,1596524400"; d="scan'208";a="157958464" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Nov 2020 06:12:54 -0800 IronPort-SDR: JaQjYtJA3G9Y50JoJsCDeIgFZGT6JtRxsbfHbglGPCdsa4F2R6v92p2NrtZSkAH2RcW1ADX5+k l9PbkGI4Q3aw== X-IronPort-AV: E=Sophos;i="5.77,485,1596524400"; d="scan'208";a="475935985" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.213.210.196]) ([10.213.210.196]) by orsmga004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Nov 2020 06:12:52 -0800 To: Andrew Rybchenko , Ivan Malov , dev@dpdk.org Cc: Thomas Monjalon , Ori Kam , Matan Azrad , Ajit Khaparde References: <20201116194029.15646-1-ivan.malov@oktetlabs.ru> From: Ferruh Yigit Message-ID: Date: Tue, 17 Nov 2020 14:12:48 +0000 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH] net/sfc: rely on native thread safety in RTE flow mechanism X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 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" On 11/17/2020 7:38 AM, Andrew Rybchenko wrote: > On 11/16/20 10:40 PM, Ivan Malov wrote: >> The changeset that introduced common flow API thread safety >> in fact introduced double locking to this particular PMD as >> RTE flow API implementation in the PMD has been thread-safe >> since the day zero. State this by setting the corresponding >> device flag to skip locking imposed by generic RTE flow API. >> >> Fixes: 80d1a9aff7f6 ("ethdev: make flow API thread safe") >> >> Signed-off-by: Ivan Malov > > Acked-by: Andrew Rybchenko > Applied to dpdk-next-net/main, thanks.