From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH v3 01/15] eal: introduce atomic exchange operation Date: Thu, 11 Jan 2018 17:01:10 +0000 Message-ID: References: <20180108174514.14688-1-stephen@networkplumber.org> <20180108174514.14688-2-stephen@networkplumber.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit To: Stephen Hemminger , dev@dpdk.org Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id EA1027288 for ; Thu, 11 Jan 2018 18:01:13 +0100 (CET) In-Reply-To: <20180108174514.14688-2-stephen@networkplumber.org> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 1/8/2018 5:45 PM, Stephen Hemminger wrote: > To handle atomic update of link status (64 bit), every driver > was doing its own version using cmpset. > Atomic exchange is a useful primitive in its own right; > therefore make it a EAL routine. > > Signed-off-by: Stephen Hemminger <...> > @@ -98,6 +98,18 @@ rte_atomic64_cmpset(volatile uint64_t *dst, uint64_t exp, uint64_t src) > return res; > } > > +static inline uint64_t > +rte_atomic64_exchange(volatile uint64_t *dest, uint64_t val) > +{ > + uint64_t old; > + > + do { > + old = *dest; > + } while (rte_atomic64_t_cmpset(dest, old, val)); rte_atomic64_cmpset ? (without _t) > + > + return old; > +} <...>