From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id E46451B3FB for ; Thu, 4 Apr 2019 17:42:08 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 786F6228BA; Thu, 4 Apr 2019 11:42:08 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 04 Apr 2019 11:42:08 -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=XSaeQG3LG8yhfNad3RBchpfjGnc7BoEeLY3QoTWu7QE=; b=Dix75q86rmsp K4cr/8t0foELQXn7czr0lL12FrES7nL9JJlqPDUBY65d2xN8CzU3TtRl81kH2kKd RHjaS+8VmC9UqFtiAnLUCG/5cLHgCMKqEPtTn9RjNm7opYpFpQAW0hNnNY/78wiG 7zQw+I3VUFC92byn+S8etXcAxw5kt8A= 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=fm2; bh=XSaeQG3LG8yhfNad3RBchpfjGnc7BoEeLY3QoTWu7 QE=; b=yLFBl+fo7lhk95bgoGjMn1Rsh8KTozgFNO0gd0U1H6Ao8EbUffF4PHO4T /aCVz7ZJjszzrVeC88/tdbOaLkXg4PBJTBEnOvgEgZznDFKhoJIoeSMmG1uBeu2b PO+ea7g0UlTKSV0MLa+iQKuf3BeMRCjxzjJDwMJoeOVcKVMiaIZwLEVUrKpNX3/d XCjPEjMJcf5s1ACkS3Edd4MhmeMJb/CxFvDwa3NH1SwM+5Xp15jW7aKmDhTco3yr QT/B+5xdTDBYoYPxGiWkgeTR7nQVopZVkw7bt7mjUybIG35+r0WmNsB5/kq4TQq2 rvWclr8eE3w/k4ur79eVyeJYhBHeQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrtdehgdeludculddtuddrgedutddrtddtmd cutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivg hnthhsucdlqddutddtmdenucfjughrpefhvffufffkjghfggfgtgesthfuredttddtvden ucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrg hlohhnrdhnvghtqeenucfkphepjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhep mhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsth gvrhfuihiivgeptd 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 D934010310; Thu, 4 Apr 2019 11:42:01 -0400 (EDT) From: Thomas Monjalon To: Gage Eads Cc: dev@dpdk.org, olivier.matz@6wind.com, arybchenko@solarflare.com, bruce.richardson@intel.com, konstantin.ananyev@intel.com, gavin.hu@arm.com, Honnappa.Nagarahalli@arm.com, nd@arm.com Date: Thu, 04 Apr 2019 17:42:00 +0200 Message-ID: <5016355.bjjE8KkVVH@xps> In-Reply-To: <20190404100127.29381-1-gage.eads@intel.com> References: <20190403232020.12784-1-gage.eads@intel.com> <20190404100127.29381-1-gage.eads@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v10 0/8] Add stack library and new mempool handler 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, 04 Apr 2019 15:42:09 -0000 04/04/2019 12:01, Gage Eads: > This patchset introduces a stack library, supporting both lock-based and > lock-free stacks, and a lock-free stack mempool handler. > > The lock-based stack code is derived from the existing stack mempool handler, > and that handler is refactored to use the stack library. > > The lock-free stack mempool handler is intended for usages where the rte > ring's "non-preemptive" constraint is not acceptable; for example, if the > application uses a mixture of pinned high-priority threads and multiplexed > low-priority threads that share a mempool. > > Note that the lock-free algorithm relies on a 128-bit compare-and-swap[1], > so it is currently limited to the x86_64 platform. [...] > Gage Eads (8): > stack: introduce rte stack library > mempool/stack: convert mempool to use rte stack > test/stack: add stack test > test/stack: add stack perf test > stack: add lock-free stack implementation > stack: add C11 atomic implementation > test/stack: add lock-free stack tests > mempool/stack: add lock-free stack mempool handler Applied (with a few minor changes), thanks for bringing this new library. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id BC54DA0679 for ; Thu, 4 Apr 2019 17:42:10 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 5E0101B419; Thu, 4 Apr 2019 17:42:10 +0200 (CEST) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id E46451B3FB for ; Thu, 4 Apr 2019 17:42:08 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 786F6228BA; Thu, 4 Apr 2019 11:42:08 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 04 Apr 2019 11:42:08 -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=XSaeQG3LG8yhfNad3RBchpfjGnc7BoEeLY3QoTWu7QE=; b=Dix75q86rmsp K4cr/8t0foELQXn7czr0lL12FrES7nL9JJlqPDUBY65d2xN8CzU3TtRl81kH2kKd RHjaS+8VmC9UqFtiAnLUCG/5cLHgCMKqEPtTn9RjNm7opYpFpQAW0hNnNY/78wiG 7zQw+I3VUFC92byn+S8etXcAxw5kt8A= 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=fm2; bh=XSaeQG3LG8yhfNad3RBchpfjGnc7BoEeLY3QoTWu7 QE=; b=yLFBl+fo7lhk95bgoGjMn1Rsh8KTozgFNO0gd0U1H6Ao8EbUffF4PHO4T /aCVz7ZJjszzrVeC88/tdbOaLkXg4PBJTBEnOvgEgZznDFKhoJIoeSMmG1uBeu2b PO+ea7g0UlTKSV0MLa+iQKuf3BeMRCjxzjJDwMJoeOVcKVMiaIZwLEVUrKpNX3/d XCjPEjMJcf5s1ACkS3Edd4MhmeMJb/CxFvDwa3NH1SwM+5Xp15jW7aKmDhTco3yr QT/B+5xdTDBYoYPxGiWkgeTR7nQVopZVkw7bt7mjUybIG35+r0WmNsB5/kq4TQq2 rvWclr8eE3w/k4ur79eVyeJYhBHeQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrtdehgdeludculddtuddrgedutddrtddtmd cutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivg hnthhsucdlqddutddtmdenucfjughrpefhvffufffkjghfggfgtgesthfuredttddtvden ucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrg hlohhnrdhnvghtqeenucfkphepjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhep mhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsth gvrhfuihiivgeptd 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 D934010310; Thu, 4 Apr 2019 11:42:01 -0400 (EDT) From: Thomas Monjalon To: Gage Eads Cc: dev@dpdk.org, olivier.matz@6wind.com, arybchenko@solarflare.com, bruce.richardson@intel.com, konstantin.ananyev@intel.com, gavin.hu@arm.com, Honnappa.Nagarahalli@arm.com, nd@arm.com Date: Thu, 04 Apr 2019 17:42:00 +0200 Message-ID: <5016355.bjjE8KkVVH@xps> In-Reply-To: <20190404100127.29381-1-gage.eads@intel.com> References: <20190403232020.12784-1-gage.eads@intel.com> <20190404100127.29381-1-gage.eads@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH v10 0/8] Add stack library and new mempool handler 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" Message-ID: <20190404154200.oseNKjOYNNMduLZWKDLhPxKvXmJ5NAH0tTk65-zUSw4@z> 04/04/2019 12:01, Gage Eads: > This patchset introduces a stack library, supporting both lock-based and > lock-free stacks, and a lock-free stack mempool handler. > > The lock-based stack code is derived from the existing stack mempool handler, > and that handler is refactored to use the stack library. > > The lock-free stack mempool handler is intended for usages where the rte > ring's "non-preemptive" constraint is not acceptable; for example, if the > application uses a mixture of pinned high-priority threads and multiplexed > low-priority threads that share a mempool. > > Note that the lock-free algorithm relies on a 128-bit compare-and-swap[1], > so it is currently limited to the x86_64 platform. [...] > Gage Eads (8): > stack: introduce rte stack library > mempool/stack: convert mempool to use rte stack > test/stack: add stack test > test/stack: add stack perf test > stack: add lock-free stack implementation > stack: add C11 atomic implementation > test/stack: add lock-free stack tests > mempool/stack: add lock-free stack mempool handler Applied (with a few minor changes), thanks for bringing this new library.