[dpdk-dev] [PATCH v3 1/3] ring: read tail using atomic load
Ananyev, Konstantin
konstantin.ananyev at intel.com
Fri Oct 5 15:44:41 CEST 2018
> -----Original Message-----
> From: Ola Liljedahl [mailto:Ola.Liljedahl at arm.com]
> Sent: Friday, October 5, 2018 12:37 PM
> To: Ananyev, Konstantin <konstantin.ananyev at intel.com>; Gavin Hu (Arm Technology China) <Gavin.Hu at arm.com>; Jerin Jacob
> <jerin.jacob at caviumnetworks.com>
> Cc: dev at dpdk.org; Honnappa Nagarahalli <Honnappa.Nagarahalli at arm.com>; Steve Capper <Steve.Capper at arm.com>; nd
> <nd at arm.com>; stable at dpdk.org
> Subject: Re: [PATCH v3 1/3] ring: read tail using atomic load
>
> https://en.cppreference.com/w/cpp/language/memory_model
> <quote>
> When an evaluation of an expression writes to a memory location and another evaluation reads or modifies the same memory location, the
> expressions are said to conflict. A program that has two conflicting evaluations has a data race unless
>
> * both evaluations execute on the same thread or in the same signal handler, or
> * both conflicting evaluations are atomic operations (see std::atomic), or
> * one of the conflicting evaluations happens-before another (see std::memory_order)
> If a data race occurs, the behavior of the program is undefined.
> </quote>
>
> C11 and C++11 have the same memory model (otherwise interoperability would be difficult).
>
> Or as Jeff Preshing explains it:
> "Any time two threads operate on a shared variable concurrently, and one of those operations performs a write, both threads must use
> atomic operations."
> https://preshing.com/20130618/atomic-vs-non-atomic-operations/
>
> So if ht->tail is written using e.g. __atomic_store_n(&ht->tail, val, mo), we need to also read it using e.g. __atomic_load_n().
>
> -- Ola
>
>
> On 05/10/2018, 13:15, "Ola Liljedahl" <Ola.Liljedahl at arm.com> wrote:
>
>
>
> On 05/10/2018, 10:22, "Ananyev, Konstantin" <konstantin.ananyev at intel.com> wrote:
>
>
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Gavin Hu (Arm Technology China)
> > Sent: Friday, October 5, 2018 1:47 AM
> > To: Jerin Jacob <jerin.jacob at caviumnetworks.com>
> > Cc: dev at dpdk.org; Honnappa Nagarahalli <Honnappa.Nagarahalli at arm.com>; Steve Capper <Steve.Capper at arm.com>; Ola
> Liljedahl
> > <Ola.Liljedahl at arm.com>; nd <nd at arm.com>; stable at dpdk.org
> > Subject: Re: [dpdk-dev] [PATCH v3 1/3] ring: read tail using atomic load
> >
> > Hi Jerin,
> >
> > Thanks for your review, inline comments from our internal discussions.
> >
> > BR. Gavin
> >
> > > -----Original Message-----
> > > From: Jerin Jacob <jerin.jacob at caviumnetworks.com>
> > > Sent: Saturday, September 29, 2018 6:49 PM
> > > To: Gavin Hu (Arm Technology China) <Gavin.Hu at arm.com>
> > > Cc: dev at dpdk.org; Honnappa Nagarahalli
> > > <Honnappa.Nagarahalli at arm.com>; Steve Capper
> > > <Steve.Capper at arm.com>; Ola Liljedahl <Ola.Liljedahl at arm.com>; nd
> > > <nd at arm.com>; stable at dpdk.org
> > > Subject: Re: [PATCH v3 1/3] ring: read tail using atomic load
> > >
> > > -----Original Message-----
> > > > Date: Mon, 17 Sep 2018 16:17:22 +0800
> > > > From: Gavin Hu <gavin.hu at arm.com>
> > > > To: dev at dpdk.org
> > > > CC: gavin.hu at arm.com, Honnappa.Nagarahalli at arm.com,
> > > > steve.capper at arm.com, Ola.Liljedahl at arm.com,
> > > > jerin.jacob at caviumnetworks.com, nd at arm.com, stable at dpdk.org
> > > > Subject: [PATCH v3 1/3] ring: read tail using atomic load
> > > > X-Mailer: git-send-email 2.7.4
> > > >
> > > > External Email
> > > >
> > > > In update_tail, read ht->tail using __atomic_load.Although the
> > > > compiler currently seems to be doing the right thing even without
> > > > _atomic_load, we don't want to give the compiler freedom to optimise
> > > > what should be an atomic load, it should not be arbitarily moved
> > > > around.
> > > >
> > > > Fixes: 39368ebfc6 ("ring: introduce C11 memory model barrier option")
> > > > Cc: stable at dpdk.org
> > > >
> > > > Signed-off-by: Gavin Hu <gavin.hu at arm.com>
> > > > Reviewed-by: Honnappa Nagarahalli <Honnappa.Nagarahalli at arm.com>
> > > > Reviewed-by: Steve Capper <steve.capper at arm.com>
> > > > Reviewed-by: Ola Liljedahl <Ola.Liljedahl at arm.com>
> > > > ---
> > > > lib/librte_ring/rte_ring_c11_mem.h | 3 ++-
> > > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > > >
> > The read of ht->tail needs to be atomic, a non-atomic read would not be correct.
>
> That's a 32bit value load.
> AFAIK on all CPUs that we support it is an atomic operation.
> [Ola] But that the ordinary C load is translated to an atomic load for the target architecture is incidental.
>
> If the design requires an atomic load (which is the case here), we should use an atomic load on the language level. Then we can be sure it
> will always be translated to an atomic load for the target in question or compilation will fail. We don't have to depend on assumptions.
We all know that 32bit load/store on cpu we support - are atomic.
If it wouldn't be the case - DPDK would be broken in dozen places.
So what the point to pretend that "it might be not atomic" if we do know for sure that it is?
I do understand that you want to use atomic_load(relaxed) here for consistency,
and to conform with C11 mem-model and I don't see any harm in that.
But argument that we shouldn't assume 32bit load/store ops as atomic sounds a bit flaky to me.
Konstantin
>
>
>
> > But there are no memory ordering requirements (with
> > regards to other loads and/or stores by this thread) so relaxed memory order is sufficient.
> > Another aspect of using __atomic_load_n() is that the compiler cannot "optimise" this load (e.g. combine, hoist etc), it has to be done
> as
> > specified in the source code which is also what we need here.
>
> I think Jerin points that rte_pause() acts here as compiler barrier too,
> so no need to worry that compiler would optimize out the loop.
> [Ola] Sorry missed that. But the barrier behaviour of rte_pause() is not part of C11, is it essentially a hand-made feature to support the
> legacy multithreaded memory model (which uses explicit HW and compiler barriers). I'd prefer code using the C11 memory model not to
> depend on such legacy features.
>
>
>
> Konstantin
>
> >
> > One point worth mentioning though is that this change is for the rte_ring_c11_mem.h file, not the legacy ring. It may be worth
> persisting
> > with getting the C11 code right when people are less excited about sending a release out?
> >
> > We can explain that for C11 we would prefer to do loads and stores as per the C11 memory model. In the case of rte_ring, the code is
> > separated cleanly into C11 specific files anyway.
> >
> > I think reading ht->tail using __atomic_load_n() is the most appropriate way. We show that ht->tail is used for synchronization, we
> > acknowledge that ht->tail may be written by other threads without any other kind of synchronization (e.g. no lock involved) and we
> require
> > an atomic load (any write to ht->tail must also be atomic).
> >
> > Using volatile and explicit compiler (or processor) memory barriers (fences) is the legacy pre-C11 way of accomplishing these things.
> There's
> > a reason why C11/C++11 moved away from the old ways.
> > > >
> > > > __atomic_store_n(&ht->tail, new_val, __ATOMIC_RELEASE);
> > > > --
> > > > 2.7.4
> > > >
>
>
>
More information about the dev
mailing list