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 27DBEA0A0C for ; Tue, 3 Aug 2021 14:23:26 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 20DE5411D6; Tue, 3 Aug 2021 14:23:26 +0200 (CEST) Received: from mail-wr1-f49.google.com (mail-wr1-f49.google.com [209.85.221.49]) by mails.dpdk.org (Postfix) with ESMTP id 195B940E3C for ; Tue, 3 Aug 2021 14:23:24 +0200 (CEST) Received: by mail-wr1-f49.google.com with SMTP id m12so20321583wru.12 for ; Tue, 03 Aug 2021 05:23:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=aHmHwYRCfe48RMGTvp6Q/6y75UxN8TYDzKT2X5NoVns=; b=jy2wPXmChr++w72pKKlbVOHH23LGoda0zzM3L9QhuihYrRKykhZk01jHlG5y6OHpEq 8qc+Gj18cwybqKRaD586BLJ7YFKw1WQ5vHK3JWHAmOmBKSZHDVKTiTTjx4FvSf3kLKh0 eoEX7z0IX4Gr/cXNrJL0fGV5qw9tsmOtN3gssRAcU6zosk2NvTuMhfJIcyCwXbimy+Tv t4PfEG7mosYKyiT+NMYaoYZpZAH4IyVlB2q226ZzaP9Xhlhp6mGOSqPRM5s9g1gOZj2W aiFYR3M0ZIaa3ecEauKK+ZHKWzcgiDLa8Gg6SBMV+/hOBk5yV0XkyuPd4eWGdpOo0tw2 E+Wg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=aHmHwYRCfe48RMGTvp6Q/6y75UxN8TYDzKT2X5NoVns=; b=RNBV1zhxt1QA1GOhAKX5fKdL56kic09Tr18ZVmixVsDsidfw5a/yXU7InzL56ZGSw3 JMjlVqDxKqJwjMR7eGqvByMxieURjdc8AMW6sB+J4oiKK0F0hTHy8CWKnOZ2mPtoe8HI 6OMdEIlfqqw6HVMYKteFTEzqZIyw2fPVPno655Ez9sz7FiaI7AvC6f9TaOx6Lo5yXIpg 6TuwKx6KAD+Eqax+s2pM/6N0N473nuVsLJGa+D6t/0Wk7haFFrqCAbdDXfAXzf2D1Bvo ftDjhUadiBcTc5sRQ1GownjWPom2UR4wQJGDSBgwOxbZzGKgjzE18zmbxsKY5sAI4PuQ aZOA== X-Gm-Message-State: AOAM533pSHtnohfVKYcqUf887/mM3GCC9veeHOnY+HnqJFq/cgs7ZbfT iQaYrJUpG75fFLNoQZfd//8= X-Google-Smtp-Source: ABdhPJy5c62/boU/nLWj2Lm9lRJt/QoVkdIg2bXJKuYf4Q1l8INqeLuCB+Rhilh9SQBBALCwUWNGQA== X-Received: by 2002:a5d:6102:: with SMTP id v2mr22120582wrt.223.1627993403871; Tue, 03 Aug 2021 05:23:23 -0700 (PDT) Received: from localhost ([137.220.125.106]) by smtp.gmail.com with ESMTPSA id a207sm2877792wme.27.2021.08.03.05.23.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 03 Aug 2021 05:23:23 -0700 (PDT) From: luca.boccassi@gmail.com To: Joyce Kong Cc: Ruifeng Wang , dpdk stable Date: Tue, 3 Aug 2021 13:22:14 +0100 Message-Id: <20210803122214.1094992-25-luca.boccassi@gmail.com> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20210803122214.1094992-1-luca.boccassi@gmail.com> References: <20210726135322.149850-59-luca.boccassi@gmail.com> <20210803122214.1094992-1-luca.boccassi@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-stable] patch 'doc: update atomic operation deprecation' has been queued to stable release 20.11.3 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" Hi, FYI, your patch has been queued to stable release 20.11.3 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 08/05/21. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. This will indicate if there was any rebasing needed to apply to the stable branch. If there were code changes for rebasing (ie: not only metadata diffs), please double check that the rebase was correctly done. Queued patches are on a temporary branch at: https://github.com/bluca/dpdk-stable This queued commit can be viewed at: https://github.com/bluca/dpdk-stable/commit/12cc60e507cb0e34523ed5629abe7b957a75b652 Thanks. Luca Boccassi --- >From 12cc60e507cb0e34523ed5629abe7b957a75b652 Mon Sep 17 00:00:00 2001 From: Joyce Kong Date: Fri, 23 Jul 2021 04:49:43 -0500 Subject: [PATCH] doc: update atomic operation deprecation [ upstream commit 3ec965b6de12bf4454d12823a28b5bbe37bd1ce5 ] Update the incorrect description about atomic operations with provided wrappers in deprecation doc[1]. [1]https://mails.dpdk.org/archives/dev/2021-July/213333.html Fixes: 7518c5c4ae6a ("doc: announce adoption of C11 atomic operations semantics") Signed-off-by: Joyce Kong Reviewed-by: Ruifeng Wang --- doc/guides/rel_notes/deprecation.rst | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index 95e3f286b5..c0d7efaba8 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -27,16 +27,18 @@ Deprecation Notices * rte_atomicNN_xxx: These APIs do not take memory order parameter. This does not allow for writing optimized code for all the CPU architectures supported - in DPDK. DPDK will adopt C11 atomic operations semantics and provide wrappers - using C11 atomic built-ins. These wrappers must be used for patches that - need to be merged in 20.08 onwards. This change will not introduce any - performance degradation. + in DPDK. DPDK has adopted the atomic operations from + https://gcc.gnu.org/onlinedocs/gcc/_005f_005fatomic-Builtins.html. These + operations must be used for patches that need to be merged in 20.08 onwards. + This change will not introduce any performance degradation. * rte_smp_*mb: These APIs provide full barrier functionality. However, many - use cases do not require full barriers. To support such use cases, DPDK will - adopt C11 barrier semantics and provide wrappers using C11 atomic built-ins. - These wrappers must be used for patches that need to be merged in 20.08 - onwards. This change will not introduce any performance degradation. + use cases do not require full barriers. To support such use cases, DPDK has + adopted atomic operations from + https://gcc.gnu.org/onlinedocs/gcc/_005f_005fatomic-Builtins.html. These + operations and a new wrapper ``rte_atomic_thread_fence`` instead of + ``__atomic_thread_fence`` must be used for patches that need to be merged in + 20.08 onwards. This change will not introduce any performance degradation. * lib: will fix extending some enum/define breaking the ABI. There are multiple samples in DPDK that enum/define terminated with a ``.*MAX.*`` value which is -- 2.30.2 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2021-08-03 12:35:09.193467310 +0100 +++ 0025-doc-update-atomic-operation-deprecation.patch 2021-08-03 12:35:08.262819688 +0100 @@ -1 +1 @@ -From 3ec965b6de12bf4454d12823a28b5bbe37bd1ce5 Mon Sep 17 00:00:00 2001 +From 12cc60e507cb0e34523ed5629abe7b957a75b652 Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit 3ec965b6de12bf4454d12823a28b5bbe37bd1ce5 ] + @@ -12 +13,0 @@ -Cc: stable@dpdk.org @@ -21 +22 @@ -index 61fadef915..92db9e14bb 100644 +index 95e3f286b5..c0d7efaba8 100644 @@ -24 +25 @@ -@@ -19,16 +19,18 @@ Deprecation Notices +@@ -27,16 +27,18 @@ Deprecation Notices