> > As agreed in the DPDK tech board [1], after 20.05 release, patches must > > use C11 atomic operations semantics with the help of wrappers. > > > > [1] http://mails.dpdk.org/archives/dev/2020-April/165143.html > > > > Signed-off-by: Honnappa Nagarahalli <honnappa.nagaraha...@arm.com> > > Reviewed-by: Phil Yang <phil.y...@arm.com> > > Reviewed-by: Ruifeng Wang <ruifeng.w...@arm.com> > > Acked-by: Hemant Agrawal <hemant.agra...@nxp.com> > > Acked-by: Jerin Jacob <jer...@marvell.com> > > --- > > +* 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. > > + > > +* 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. > > Acked-by: Konstantin Ananyev <konstantin.anan...@intel.com> Acked-by: David Christensen <d...@linux.vnet.ibm.com>
Applied, thanks
