From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 60F27A04DB;
	Tue, 17 Nov 2020 08:38:18 +0100 (CET)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id 8BC0E37B1;
	Tue, 17 Nov 2020 08:38:16 +0100 (CET)
Received: from shelob.oktetlabs.ru (shelob.oktetlabs.ru [91.220.146.113])
 by dpdk.org (Postfix) with ESMTP id 03CCD37B0
 for <dev@dpdk.org>; Tue, 17 Nov 2020 08:38:13 +0100 (CET)
Received: from [192.168.38.17] (aros.oktetlabs.ru [192.168.38.17])
 (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested)
 by shelob.oktetlabs.ru (Postfix) with ESMTPSA id 713BB7F4F8;
 Tue, 17 Nov 2020 10:38:12 +0300 (MSK)
DKIM-Filter: OpenDKIM Filter v2.11.0 shelob.oktetlabs.ru 713BB7F4F8
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=oktetlabs.ru;
 s=default; t=1605598692;
 bh=FMAfssPiYzG+EXX+h/KwyLgcSTMU5frKtmGXSzZsbSE=;
 h=Subject:To:Cc:References:From:Date:In-Reply-To;
 b=Z1Nc1ZNfBT+r+Myc7N862pwR9VC5os+LhOtPOjjrl8cdEYFWLpF5kRo/JQqcO+oW8
 FBipML8ClqhUCfKB83OCh8HlsjdH76a6Em/UJub2YhFvU2N0w13jFDmhxC+qeGIgQ4
 u1Npdh9Y0W8uhx35q5yHlofSpyNoKX73o6AdWXvM=
To: Ivan Malov <ivan.malov@oktetlabs.ru>, dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>, Ori Kam <orika@nvidia.com>,
 Matan Azrad <matan@nvidia.com>, Ajit Khaparde <ajit.khaparde@broadcom.com>
References: <20201116194029.15646-1-ivan.malov@oktetlabs.ru>
From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Organization: OKTET Labs
Message-ID: <fe10bd14-e8fc-ca97-0c73-f0b01797b865@oktetlabs.ru>
Date: Tue, 17 Nov 2020 10:38:12 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.4.0
MIME-Version: 1.0
In-Reply-To: <20201116194029.15646-1-ivan.malov@oktetlabs.ru>
Content-Type: text/plain; charset=utf-8
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 <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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 <ivan.malov@oktetlabs.ru>

Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>