From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 0062E1B061 for ; Thu, 12 Jul 2018 23:03:09 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 7EBEC2226C; Thu, 12 Jul 2018 17:03:09 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 12 Jul 2018 17:03:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=RULN1v7C5oYGJsiWTAFxb91uma dX1BpfeGIwyO8AJJM=; b=R6FGi2+uVLggN63RiU1GHH5OXrD9mD9bxW0AlGzRT6 0Oy1xqVSia4Y2S5DMs+BJJ1XG6nEBwalYE1xlhzfrjnHEw0UkjfLQbRY/5NoEOK8 uurUYC8BXK96pkm87N59PV4mXpOlrlFpEYEPr3OPx8h3S6dTC2/dliGe4X7k4D8n U= 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-sender:x-me-sender:x-sasl-enc; s=fm3; bh=RULN1v 7C5oYGJsiWTAFxb91umadX1BpfeGIwyO8AJJM=; b=WdouRC/6yqxHmanGERzU7Q KvLpsRJ71FDvUecdJUaWZUyBRQS8JXbbHuiamNIoIi+nQ1AYP53P2gGo1MzaNZEG tASwTJzoDWgH26euZM+D7yCsabwfJGQZJN+SFG3t41JVSJQW6+zfFS5625QZFCic DMreJCSSvactkAZFarzuiW/AO8Y+eXwl6CV4gHi55leemxgEG+iKQ7EYwwVWXTH+ VYsjysvsxNNIM+20sdR+hCiaofg7i8mOlMbnYRJ2dOMkxfnqSQowBblLJis/DFaY RZn7KTT8cqxagLGqSo9Kx1EZzlUMwG416ZtfACLRbwtqkis4Mo6oCicQJyWEduMw == X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 23D061025C; Thu, 12 Jul 2018 17:03:08 -0400 (EDT) From: Thomas Monjalon To: Yipeng Wang Cc: dev@dpdk.org, pablo.de.lara.guarch@intel.com, bruce.richardson@intel.com, honnappa.nagarahalli@arm.com, vguvva@caviumnetworks.com, brijesh.s.singh@gmail.com Date: Thu, 12 Jul 2018 23:03:06 +0200 Message-ID: <3745102.CzknF7dljW@xps> In-Reply-To: <1531242001-381104-1-git-send-email-yipeng1.wang@intel.com> References: <1528455078-328182-1-git-send-email-yipeng1.wang@intel.com> <1531242001-381104-1-git-send-email-yipeng1.wang@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v5 0/8] Add read-write concurrency to rte_hash library 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: , X-List-Received-Date: Thu, 12 Jul 2018 21:03:10 -0000 10/07/2018 18:59, Yipeng Wang: > This patch set adds the read-write concurrency support in rte_hash. > A new flag value is added to indicate if read-write concurrency is needed > during creation time. Test cases are implemented to do functional and > performance tests. > > The new concurrency model is based on rte_rwlock. When Intel TSX is > available and the users indicate to use it, the TM version of the > rte_rwlock will be called. Both multi-writer and read-write concurrency > are protected by the rte_rwlock instead of the x86 specific RTM > instructions, so the x86 specific header rte_cuckoo_hash_x86.h is removed > and the code is infused into the main .c file. > > A new rte_hash_count API is proposed to count how many keys are inserted > into the hash table. > > Yipeng Wang (8): > hash: fix multiwriter lock memory allocation > hash: fix a multi-writer race condition > hash: fix key slot size accuracy > hash: make duplicated code into functions > hash: add read and write concurrency support > test: add tests in hash table perf test > test: add test case for read write concurrency > hash: add new API function to query the key count Applied, thanks