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 BE422A0527; Mon, 20 Jul 2020 17:34:11 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 4F21E1BFBC; Mon, 20 Jul 2020 17:34:10 +0200 (CEST) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 562AC1BFBB; Mon, 20 Jul 2020 17:34:08 +0200 (CEST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 44AAA5C00BC; Mon, 20 Jul 2020 11:34:05 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Mon, 20 Jul 2020 11:34:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding:content-type; s=fm1; bh=hgEdiPjyKo8g+ 4VP2khCkkzWZp8iO3teExQrK7pKztc=; b=rE/KVqjlPKKMQ7BAK6pm5szgUM3Uu D3CNhQUm+HqTwgKpoQ1np5fyawVVZjHuPEcpDU+NBSKuDWoIZ8C8qRkpiJ59CnmD mqRqEoynBwbvHUw3s5hyUmA+t6p8aeGKphm3Oc019KpQXP+YCXMZafQEMNk7q9iv 9NaBnU0HjBApKNp4Sm/tpCekXkwcdcebooAek+1RWUk+U1gWkzKDbiYfYrfQKtBi c7i/4r8NnH5zoo3+1EKMcqQy6NsuC2sAAFaAoAXPha0AwFd/x17mw8NIvA5xIqVC VuyOOXtHq7DD/F55tpDGZigTHtlea7R2hPQyHPVLdDR06RjO3zvLdxo0w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=hgEdiP jyKo8g+4VP2khCkkzWZp8iO3teExQrK7pKztc=; b=F19GT2O239H1Nba4GVXhqR Lox3IrCzepC8Kms/wQ2hE1bEnaZPs2mFVOB3eJ1T2Cu/Ex4vkTApBkMrNGO4MddO 7eJ7VGvCU/lvc33gbNxJMKjwGQ2k4+PbqHw/ZjgAR0IEvDBnHG58WAHHcIdFJPMY KOvV+Y7fUzVdGASXZ12Y5xhpvTcyfgRYhLcor4TY0NZiwAmeBoKCoQg6GZtBVMhw +3V1Q/SRyvFF8jYZXtUQGMgfBexXJ6LYYYtFR6LKZf61WScm8QdinAHh0LUdKTYX J+oE4ZhjDPmhWZFpGeSOamzE7rMTZqzAgZ+VQdfNmQ0kkRJDx8mld+3K6kxGK2bg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrgeeggdeihecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephffvufffkfgggfgtsehtufertddttd dvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhn jhgrlhhonhdrnhgvtheqnecuggftrfgrthhtvghrnhepffegheetveffuefffeevgeelte etieefueetteejteegvdefiedvteevjefgfeegnecuffhomhgrihhnpeguphgukhdrohhr ghenucfkphepjeejrddufeegrddvtdefrddukeegnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgv th 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 E59B730600A3; Mon, 20 Jul 2020 11:34:03 -0400 (EDT) From: Thomas Monjalon To: honnappa.nagarahalli@arm.com Cc: ferruh.yigit@intel.com, david.marchand@redhat.com, dev@dpdk.org, phil.yang@arm.com, techboard@dpdk.org Date: Mon, 20 Jul 2020 17:34:01 +0200 Message-ID: <7124002.r8JxatOC3Q@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: [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" 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. Can we make this rule better advertised with an announce message? Are the current technical explanations enough? If not, it would be wonderful to have a blog post explaining the details, as part of an announce.