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 8ED32A0527; Mon, 20 Jul 2020 18:39:11 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 149D81BFBF; Mon, 20 Jul 2020 18:39:11 +0200 (CEST) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 879152B86; Mon, 20 Jul 2020 18:39:09 +0200 (CEST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id B89545C006A; Mon, 20 Jul 2020 12:39:08 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Mon, 20 Jul 2020 12:39: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=fm1; bh= TOmUgQfUrb16O7qxHxgApjVe2rgjEwvylJXzbkV1GOg=; b=EM/7Tp4FOYfN3Jzz m1SuBsyxQOdVqNyB71VOGkYvqZgOt67p8RCQhFQxeFjfsMSPTv+ZcvvXFc2unqhR Zfa+aFZJjr8oiZyBA0DEr5bFZW1wS8/zLLkCYHuWespn1udqyEvcnsd8tXT3vVkz /MQMfqO3bqw5yvdQ01saqwOkqKoY3BwVB7G3i7bTfrHAA4dujs58kIh23mQlfNhn QS/p74zSY0gBgNJFRYJ0Psvn8jXyg0vziNjaD/cptT58lqAWDZaWDGlJDDnqqiN0 u6KcoV24fE/kuDd45bGMtY73svKUnyjyiUtU8c52YWVxi+iCsPtQdy9fSTvZNJO9 6L/hnA== 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=TOmUgQfUrb16O7qxHxgApjVe2rgjEwvylJXzbkV1G Og=; b=ZpJ2KwHl9KD94fr2lN3c6y3jWpusuZ4E8aZCEuVPCMgqGVrqhQs6ScOdw AVj8SmHwQzI4btkdifnHXzFxHYujKEvslbHeXEH1slRaV0IhG4SlaMrPbUOJo0T5 61THlIlrxzbmAZCCcWKIaFfHUk6SNY1e6sKPd8dO7C3oXZMOUjaazlreKdPcdCSb 72suVampIo3VA9VYa0xtLdMEh7MbQQfUjp/1JfQInaP2q3cwLzhh8D/jCThyvvMf GJrByQOVTl9wickYx8GhBRtQRWxpE9GOvNJLFwPjAfGRBdEd3oPwd8qfKNLGbNG3 SVkrrTuUnGdjmXUE5gvse35CxF9NA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrgeeggdejlecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpeffvdffjeeuteelfeeileduudeugfetjeelveefkeejfeeigeehteff vdekfeegudenucffohhmrghinhepughpughkrdhorhhgnecukfhppeejjedrudefgedrvd dtfedrudekgeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhr ohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght 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 37DD530600A3; Mon, 20 Jul 2020 12:39:07 -0400 (EDT) From: Thomas Monjalon To: Honnappa Nagarahalli Cc: "ferruh.yigit@intel.com" , "david.marchand@redhat.com" , "dev@dpdk.org" , Phil Yang , "techboard@dpdk.org" , nd , Ruifeng Wang Date: Mon, 20 Jul 2020 18:39:05 +0200 Message-ID: <3186466.fdGK1iNSLM@thomas> In-Reply-To: References: <7124002.r8JxatOC3Q@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] Using C11 atomic semantic 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" 20/07/2020 17:44, Honnappa Nagarahalli: > From: Thomas Monjalon > > > > In the techboard of April 22, it has been decided to block patches using > > rte_atomicNN_xx and rte_smp_*mb APIs, starting DPDK 20.08. > > Meeting minutes: > > http://mails.dpdk.org/archives/dev/2020-April/165143.html > > Deprecation notice: > > http://doc.dpdk.org/guides/rel_notes/deprecation.html > > > > Some doc has been submitted to help understanding how to manage atomics: > > http://doc .dpdk.org/guides/prog_guide/writing_efficient_code.html#locks-and- > > atomic-operations > > > > Unfortunately the tool to check new code was merged last week: > > http://git.dpdk.org/dpdk/commit/?id=f1602b4a86 > > > > As a consequence, I propose to apply the "reject rule" starting DPDK 20.11. > > As far as I know no patch with rte_atomic has gone in 20.08 so far. Are there any patches in RC2/RC3 that need rte_atomic APIs? Yes we have the case of an additional call added in 20.08-rc2 in mlx5 (not yet converted to C11 atomics). > > Can we make this rule better advertised with an announce message? > > Do you mean an email on dpdk-announce mailing list? Yes > > Are the current technical explanations enough? > > The documentation patch you referenced above covers most common cases people will encounter. Even the rte_ring/rte_stack algorithms work on the same principles. > > > If not, it would be wonderful to have a blog post explaining the details, as > > part of an announce. > > This is in the works. The plan is to send it to you soon and get it out along with the release. Great