From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 43968A0C47; Tue, 12 Oct 2021 18:32:16 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 609BB410E1; Tue, 12 Oct 2021 18:32:15 +0200 (CEST) Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com [66.111.4.221]) by mails.dpdk.org (Postfix) with ESMTP id 5C02E410DF for ; Tue, 12 Oct 2021 18:32:14 +0200 (CEST) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailnew.nyi.internal (Postfix) with ESMTP id 1186A58047C; Tue, 12 Oct 2021 12:32:14 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Tue, 12 Oct 2021 12:32:14 -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=fm2; bh= jxHE/ah6t5J3omMvRzHLuzITXjXeVaOu2NvOmibobBE=; b=pmaINWTOO51YXuP7 yU2b8KHSSDkSjZ9nJpuBjv11nzFzm5pUfwUqQI58eI2m51Rdmq+urGFdIq64YI+J 96Be6o22Q0xFWwwknLpfUR4rITSbxaY/oCRZqtxFCP/GHPG1GtlRjOz48UEdOPvj y6VlGYNxey1G23LA6LC2x7TxC/C+juYQyJGhgK4J+JozQzNTgEKgl8FOH2KXhxsc JWR3IMNl9kpvo8vR88/CRDP8RqwOAqDcH5me9Nee7QWdrS/GQBHW7rXNRMW/fvnG yrEBzvISXqeenrQz0TV7VK2ppD51IWZS99TqNNFAfJNN/bGbNgEo/yP6tGDuyAEs RzClxg== 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=jxHE/ah6t5J3omMvRzHLuzITXjXeVaOu2NvOmibob BE=; b=JiRs1M79aBK+bAvqO92EjKSsUYg7El2G5PP44EXwp96JP/y8sqYi15vuH r1j/8op1KOWk8Mbxcyb7r4mj5QG3SmJTNUg01gjtb0Dziosiq7gBG9A5+O4mw2cR 5jdT29541o4ryz5nKB3MwYH1iw19Al6vz71DYjUJkFs7tVWpRHSBSax0O0BHZEq/ LDghoVDGX9YKEgoAL+qykOHUoD75nQcM6bDNjfCMpGE7HsxPt5EVoxboTiZC0YtR WhuxXqEG3sUrkdo4rDhyQY6pKm/qYs55JPchFllxW4zlGrHlrKZhclPB/Wsta3x1 +KwbcvCJ7PirDhZ543rrJDfyXfb2w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrvddtkedgleekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepudeggfdvfeduffdtfeeglefghfeukefgfffhueejtdetuedtjeeu ieeivdffgeehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 12 Oct 2021 12:32:11 -0400 (EDT) From: Thomas Monjalon To: Narcisa Ana Maria Vasile Cc: dev@dpdk.org, dmitry.kozliuk@gmail.com, khot@microsoft.com, dmitrym@microsoft.com, roretzla@microsoft.com, talshn@nvidia.com, ocardona@microsoft.com, bruce.richardson@intel.com, david.marchand@redhat.com, pallavi.kadam@intel.com Date: Tue, 12 Oct 2021 18:32:09 +0200 Message-ID: <27236504.5ELz80oB1M@thomas> In-Reply-To: <1633765318-28356-9-git-send-email-navasile@linux.microsoft.com> References: <1633732841-17873-1-git-send-email-navasile@linux.microsoft.com> <1633765318-28356-1-git-send-email-navasile@linux.microsoft.com> <1633765318-28356-9-git-send-email-navasile@linux.microsoft.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v16 8/9] eal: implement functions for thread barrier management X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 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" 09/10/2021 09:41, Narcisa Ana Maria Vasile: > From: Narcisa Vasile > > Add functions for barrier init, destroy, wait. > > A portable type is used to represent a barrier identifier. > The rte_thread_barrier_wait() function returns the same value > on all platforms. > > Signed-off-by: Narcisa Vasile > --- > lib/eal/common/rte_thread.c | 61 ++++++++++++++++++++++++++++++++++++ > lib/eal/include/rte_thread.h | 58 ++++++++++++++++++++++++++++++++++ > lib/eal/version.map | 3 ++ > lib/eal/windows/rte_thread.c | 56 +++++++++++++++++++++++++++++++++ > 4 files changed, 178 insertions(+) It doesn't need to be part of the API. The pthread barrier is used only as part of the control thread implementation. The need disappear if you implement control thread on Windows.