[0/4] hash: separate lf and rw lock lookup code paths
Message ID | 20181109163917.16845-1-honnappa.nagarahalli@arm.com (mailing list archive) |
---|---|
Headers |
Return-Path: <dev-bounces@dpdk.org> X-Original-To: patchwork@dpdk.org Delivered-To: patchwork@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 930DD4C9F; Fri, 9 Nov 2018 17:39:44 +0100 (CET) Received: from foss.arm.com (foss.arm.com [217.140.101.70]) by dpdk.org (Postfix) with ESMTP id 8525F4C94 for <dev@dpdk.org>; Fri, 9 Nov 2018 17:39:43 +0100 (CET) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 8BABDA78; Fri, 9 Nov 2018 08:39:42 -0800 (PST) Received: from qc2400f-1.austin.arm.com (qc2400f-1.austin.arm.com [10.118.12.122]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 083D73F5BD; Fri, 9 Nov 2018 08:39:41 -0800 (PST) From: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> To: bruce.richardson@intel.com, pablo.de.lara.guarch@intel.com Cc: dev@dpdk.org, jerin.jacob@caviumnetworks.com, hemant.agrawal@nxp.com, chaozhu@linux.vnet.ibm.com, yipeng1.wang@intel.com, dharmik.thakkar@arm.com, gavin.hu@arm.com, honnappa.nagarahalli@arm.com, nd@arm.com Date: Fri, 9 Nov 2018 10:39:13 -0600 Message-Id: <20181109163917.16845-1-honnappa.nagarahalli@arm.com> X-Mailer: git-send-email 2.17.1 Subject: [dpdk-dev] [PATCH 0/4] hash: separate lf and rw lock lookup code paths 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> |
Message
Honnappa Nagarahalli
Nov. 9, 2018, 4:39 p.m. UTC
The lock-free algorithm has caused significant lookup performance regression for certain use cases. The regression is attributed to the use of non-relaxed memory orderings. To address the issue, 2 versions of the lookup functions are created. One that uses the RW lock and the one that is lock-free. This restores the performance regression caused for use cases that used RW lock version of the lookup function. This series has been split into 4 commits to make the review process easier. All of these should be squashed into a single commit after the review process is over. Honnappa Nagarahalli (4): hash: prepare for lock-free and rw-lock separation hash: remove rw-lock calls from lock-free functions hash: remove memory orderings from rw-lock lookup fns hash: separate lf and rw lock lookup code paths lib/librte_hash/rte_cuckoo_hash.c | 303 ++++++++++++++++++++++++++++-- 1 file changed, 289 insertions(+), 14 deletions(-)