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 B3CF343B39; Sun, 18 Feb 2024 13:18:12 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 35B2C4028A; Sun, 18 Feb 2024 13:18:12 +0100 (CET) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by mails.dpdk.org (Postfix) with ESMTP id 6EBC240262 for ; Sun, 18 Feb 2024 13:18:11 +0100 (CET) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 32CB93200A13; Sun, 18 Feb 2024 07:18:07 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Sun, 18 Feb 2024 07:18:08 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1708258686; x=1708345086; bh=b4HYiditXAQBvcL9Kbgz4UdrV6OlTlKn7EV7wYIIAkI=; b= yYQUiXtZk8lc3s2KXDeHNy5TXXCk45VRTsmP7qB0e+adUgkQuSSAj2HIUmEb8LTP 4v1GFXdHn3vv04TcdpAvMzSwUYrUCKq9k5XScRr5iQSfgMYG2jgG5AvIbxnOcqVe R9bWvCligEGz5NmepcLp0LEnWGPNtOx/MTJMYzE/90B9DDtE2cfkJVv+zDTzD0uT /mGRxq8oMil3rJpPk1KKUu4TBsKPDZVsUSpC7PfJ/0ycc0NYwUmsVGddtNDfJ1jr X7nlprS+3s2zwTb6cyEvg3fqKhDq8wr3QXnbwpNtKZCULBc6jVtyRVpM/XFHjWiP RRIejUAVW1e29X9eZxUmxQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1708258686; x= 1708345086; bh=b4HYiditXAQBvcL9Kbgz4UdrV6OlTlKn7EV7wYIIAkI=; b=S twiIc51EitRGAE0E//CiebE5ry/l4t+vk97U6HOcBVYEQWikUpG+82XfTUUEjlid t/5dT5gv3KrW0vkn4GHh76qwAsp3YOMBbD76LGq/hIyKp61R8RE3mz7L9VxxAL1T mst2HJGft8l5TwPLFLUqx8LGySDuH6bayf3gH3gMEzUDwYQQP7ssEF8nDkcGl1E7 bzOBH9vqZ1m0D4QwzpyMF9BGSLIso4orIboZ34fwh69HucO//iBQrmqJykbP/Acf wEuCE8luv/k020F/41XD78AUg0g4hKAoT6jQIsEaCdH+MI9DhAAuNrhR1P06y25C tY7qsNLlPEccd9mVksmgA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdeigdeflecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvfevufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnheptdejieeifeehtdffgfdvleetueeffeehueejgfeuteeftddtieek gfekudehtdfgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 18 Feb 2024 07:18:04 -0500 (EST) From: Thomas Monjalon To: Tyler Retzlaff Cc: dev@dpdk.org, Bruce Richardson , David Hunt , Honnappa Nagarahalli , Jerin Jacob , Konstantin Ananyev , Sameh Gobriel , Sunil Kumar Kori , Vladimir Medvedkin , Yipeng Wang , mb@smartsharesystems.com, fengchengwen Subject: Re: [PATCH v2 0/6] use rte atomic thread fence Date: Sun, 18 Feb 2024 13:18:03 +0100 Message-ID: <6313232.rnE6jSC6OK@thomas> In-Reply-To: <51bce246-d633-d41b-a62c-c9c5ae9fcb4c@huawei.com> References: <1698894265-22963-1-git-send-email-roretzla@linux.microsoft.com> <1707979859-3984-1-git-send-email-roretzla@linux.microsoft.com> <51bce246-d633-d41b-a62c-c9c5ae9fcb4c@huawei.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 > > Replace use of __atomic_thread_fence with rte_atomic_thread_fence. > > > > Notes: > > > > The rest of lib/lpm will be converted to rte_atomic in a separate > > series (to be submitted soon). > > > > There are existing checkpatches checks that catch use of both > > __atomic_thread_fence and __rte_atomic_thread_fence in new > > submissions. > > > > v2: > > * change series to use rte_atomic_thread_fence instead of > > __rte_atomic_thread_fence (internal) > > * also change __atomic_thread_fence in lib/lpm > > > > Tyler Retzlaff (6): > > distributor: use rte atomic thread fence > > eal: use rte atomic thread fence > > hash: use rte atomic thread fence > > ring: use rte atomic thread fence > > stack: use rte atomic thread fence > > lpm: use rte atomic thread fence > > Series-acked-by: Chengwen Feng Acked-by: Thomas Monjalon Squashed and applied, thanks.