From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id C549E1B5E8 for ; Wed, 19 Dec 2018 03:39:43 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 3DD4B220A3; Tue, 18 Dec 2018 21:39:43 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 18 Dec 2018 21:39:43 -0500 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=L2hsY9dCzdohJC12sGvtEpwYiME/zRiK+ULTdmYMSeU=; b=Yey2ka/UUq5P wXOAy0sCfyZyziyn7GXwpesQqPMV0qNgya+nn5zbPol9NLAROib6kiICagfYpFVE dwsFWis0tuW/+JiqoY1YiMVL7c+l/hHEDKq69dWWyNCOMGwBkPPDVpBbLEPa4kRu uykTyFJgBAs92krsinl1wyhcF/Yj5Yg= 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=fm1; bh=L2hsY9dCzdohJC12sGvtEpwYiME/zRiK+ULTdmYMS eU=; b=BbDWExi8y15eXXQw+MKrOPKg19r38S10azB1DKfI4rR9sXqk5vQRS5slP YCmzBl0s9oltqE9PhsL8PwbUL5K/nSvcEg/dOU1ADkZPi20eJIk8Ax2m6c0OQRmn BpHchW4nsPKdmbiv3IrrxmczeB9q5MVvtrDZrm2LKQnu4GwlBus9p7Gvvs8FuKAD 9C7u5kFZPpIFOS4LSTVgFOIhlDQReGfvBSF6cVjVBbHOBparc+XXyNuIZ4a/Ey9F JA7XYUqkdMaa4zURhUIdfufOBVjobtUkhp8ewcLhQH1/jkCQStbK0caFPfqr2xb2 +263NBcoYQDNVBjJkXhm+YYZ+yb5A== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtkedrudeiledgvddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefhvffufffkjg hfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcu oehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkphepjeejrddufeegrddvtd efrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghl ohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd 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 85EC6E4366; Tue, 18 Dec 2018 21:39:41 -0500 (EST) From: Thomas Monjalon To: dev@dpdk.org Cc: Konstantin Ananyev , honnappa.nagarahalli@arm.com, jerinj@marvell.com, Chao Zhu Date: Wed, 19 Dec 2018 03:39:40 +0100 Message-ID: <3706402.B1puXbZNJX@xps> In-Reply-To: <1542130061-3702-1-git-send-email-konstantin.ananyev@intel.com> References: <1542130061-3702-1-git-send-email-konstantin.ananyev@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 0/2] Add 'try' semantics for RD and WR locking 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: Wed, 19 Dec 2018 02:39:44 -0000 13/11/2018 18:27, Konstantin Ananyev: > This series targets 19.02 release > > Introduce rte_rwlock_read_trylock() and rte_rwlock_write_trylock() > and new UT test-case for it. > > Konstantin Ananyev (2): > rwlock: introduce 'try' semantics for RD and WR locking > test: add new test-cases for rwlock autotest Any comment?