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 217F9A0487 for ; Thu, 4 Jul 2019 22:12:31 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id D03572C60; Thu, 4 Jul 2019 22:12:29 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 6ABA22C38 for ; Thu, 4 Jul 2019 22:12:28 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id E64D521BA9; Thu, 4 Jul 2019 16:12:27 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 04 Jul 2019 16:12:27 -0400 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=mesmtp; bh=gTPnsjnk4eInCVQROZXjiyqlKR+/4IswvQmI1FYJgr4=; b=c+wijXV686ul EwI4l3nqRwbKPlMcNkUl0FaL/193Oz1EAMbOaSCApWGSCta9TJuqP0SLHXCPBm3n wjIx/vjKtCTy8YkgxsYsK/IRHmlm9XSnHpgq2255Ccy+AEbTuY0/M73epPKvix+m pV8nehUSel3RIza8j67fRmLjF5l5OYg= 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=fm3; bh=gTPnsjnk4eInCVQROZXjiyqlKR+/4IswvQmI1FYJg r4=; b=SPin44/4SKIxOr5OaK4VKvwy+cSQ0Vx1aNCJJk5MVUGKG/V6SnKyg0Dkl RN/QhqH8R2Ib0/f79E6OWrx++zu3VNpS8dvbL8skzNrkawsqFWuuvCZZ058yBqwc AC7ikW2+SSNqGeG58NbKsTjTPmeJn0Pf03uFX0owVGmbAjEpC+JVQje1RWXQrnSE t6yVNMgFIqaHgVgSHwtVJ0K2oFuDlBJjXGnxiKhgRQVwzZFCMQO29cJV2vtDFMXh BRmwMzaI780mF7TwpHs0VmU5waBAiMLcoptwo+cNjTTxQ7rXLy792T0bsuGItEpD DFItZ2R8WlsLkbRLgO58mAOjaWJzw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrfedvgddugeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt 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 56F568005A; Thu, 4 Jul 2019 16:12:26 -0400 (EDT) From: Thomas Monjalon To: Phil Yang , Honnappa.Nagarahalli@arm.com Cc: dev@dpdk.org, jerinj@marvell.com, hemant.agrawal@nxp.com, gavin.hu@arm.com, nd@arm.com Date: Thu, 04 Jul 2019 22:12:25 +0200 Message-ID: <2092867.9Mj67vrD68@xps> In-Reply-To: <1559750328-22377-1-git-send-email-phil.yang@arm.com> References: <1559750328-22377-1-git-send-email-phil.yang@arm.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v1 0/3] MCS queued lock implementation 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" 05/06/2019 17:58, Phil Yang: > This patch set added MCS lock library and its unit test. > > The MCS lock (proposed by JOHN M. MELLOR-CRUMMEY and MICHAEL L. SCOTT) provides > scalability by spinning on a CPU/thread local variable which avoids expensive > cache bouncings. It provides fairness by maintaining a list of acquirers and > passing the lock to each CPU/thread in the order they acquired the lock. What is the plan for this patch? Do we try to get more reviews for a merge in 19.08-rc2? Or we target 19.11?