...@redhat.com;
> > Honnappa Nagarahalli ; Gavin Hu
> > ; nd ; nd
> > Subject: RE: [dpdk-dev] [PATCH v3] lib/timer: relax barrier for status
> > update
> >
> >
> >
> > > -Original Message-
> > > From: Phil Yang
> > > Sent:
; david.march...@redhat.com; Honnappa Nagarahalli
> > ; Gavin Hu ; nd
> > ; nd
> > Subject: RE: [dpdk-dev] [PATCH v3] lib/timer: relax barrier for status
> update
> >
> > > -Original Message-
> > > From: Thomas Monjalon
> > > Sent:
avid.march...@redhat.com; Honnappa Nagarahalli
> > ; Gavin Hu ; nd
> >
> > Subject: Re: [dpdk-dev] [PATCH v3] lib/timer: relax barrier for status
> > update
> >
> > 24/04/2020 09:24, Phil Yang:
> > > Volatile has no ordering semantics. The rte_timer stru
> -Original Message-
> From: Thomas Monjalon
> Sent: Sunday, April 26, 2020 1:18 AM
> To: Phil Yang
> Cc: erik.g.carri...@intel.com; rsanf...@akamai.com; dev@dpdk.org;
> david.march...@redhat.com; Honnappa Nagarahalli
> ; Gavin Hu ; nd
>
> Subject: Re: [dpd
24/04/2020 09:24, Phil Yang:
> Volatile has no ordering semantics. The rte_timer structure defines
> timer status as a volatile variable and uses the rte_r/wmb barrier
> to guarantee inter-thread visibility.
>
> This patch optimized the volatile operation with c11 atomic operations
> and one-way b
Volatile has no ordering semantics. The rte_timer structure defines
timer status as a volatile variable and uses the rte_r/wmb barrier
to guarantee inter-thread visibility.
This patch optimized the volatile operation with c11 atomic operations
and one-way barrier to save the performance penalty. A
6 matches
Mail list logo
