omas Monjalon ; Juhamatti Kuusisaari
> > ; dev at dpdk.org
> > Subject: Re: [dpdk-dev] [PATCH] lib: change rte_ring dequeue to guarantee
> > ordering before tail update
> >
> > On Sat, Jul 23, 2016 at 11:15:27AM +, Ananyev, Konstantin wrote:
> > >
> > &
omas Monjalon ; Juhamatti Kuusisaari
> > ; dev at dpdk.org
> > Subject: Re: [dpdk-dev] [PATCH] lib: change rte_ring dequeue to guarantee
> > ordering before tail update
> >
> > On Sat, Jul 23, 2016 at 10:14:51AM +, Ananyev, Konstantin wrote:
> > > Hi lads,
&g
On Sat, Jul 23, 2016 at 10:14:51AM +, Ananyev, Konstantin wrote:
> Hi lads,
>
> > On Sat, Jul 23, 2016 at 11:02:33AM +0200, Thomas Monjalon wrote:
> > > 2016-07-23 8:05 GMT+02:00 Jerin Jacob :
> > > > On Thu, Jul 21, 2016 at 11:26:50PM +0200, Thomas Monjalon wrote:
> > > >> > > Consumer queue
On Sat, Jul 23, 2016 at 11:02:33AM +0200, Thomas Monjalon wrote:
> 2016-07-23 8:05 GMT+02:00 Jerin Jacob :
> > On Thu, Jul 21, 2016 at 11:26:50PM +0200, Thomas Monjalon wrote:
> >> > > Consumer queue dequeuing must be guaranteed to be done fully before
> >> > > the tail is updated. This is not
Sent: Saturday, July 23, 2016 11:39 AM
> > > To: Ananyev, Konstantin
> > > Cc: Thomas Monjalon ; Juhamatti
> > > Kuusisaari ; dev at dpdk.org
> > > Subject: Re: [dpdk-dev] [PATCH] lib: change rte_ring dequeue to
> > > guarantee ordering b
On Thu, Jul 21, 2016 at 11:26:50PM +0200, Thomas Monjalon wrote:
> > > Consumer queue dequeuing must be guaranteed to be done fully before the
> > > tail is updated. This is not guaranteed with a read barrier,
> > > changed to a write barrier just before tail update which in practice
> > >
> -Original Message-
> From: Jerin Jacob [mailto:jerin.jacob at caviumnetworks.com]
> Sent: Saturday, July 23, 2016 11:39 AM
> To: Ananyev, Konstantin
> Cc: Thomas Monjalon ; Juhamatti Kuusisaari
> ; dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] lib: ch
2016-07-23 8:05 GMT+02:00 Jerin Jacob :
> On Thu, Jul 21, 2016 at 11:26:50PM +0200, Thomas Monjalon wrote:
>> > > Consumer queue dequeuing must be guaranteed to be done fully before the
>> > > tail is updated. This is not guaranteed with a read barrier,
>> > > changed to a write barrier just
Hi lads,
> On Sat, Jul 23, 2016 at 11:02:33AM +0200, Thomas Monjalon wrote:
> > 2016-07-23 8:05 GMT+02:00 Jerin Jacob :
> > > On Thu, Jul 21, 2016 at 11:26:50PM +0200, Thomas Monjalon wrote:
> > >> > > Consumer queue dequeuing must be guaranteed to be done fully
> > >> > > before the tail is
> > Consumer queue dequeuing must be guaranteed to be done fully before the
> > tail is updated. This is not guaranteed with a read barrier,
> > changed to a write barrier just before tail update which in practice
> > guarantees correct order of reads and writes.
> >
> > Signed-off-by:
>
> Consumer queue dequeuing must be guaranteed to be done fully before the tail
> is updated. This is not guaranteed with a read barrier,
> changed to a write barrier just before tail update which in practice
> guarantees correct order of reads and writes.
>
> Signed-off-by: Juhamatti
Consumer queue dequeuing must be guaranteed to be done fully before
the tail is updated. This is not guaranteed with a read barrier,
changed to a write barrier just before tail update which in practice
guarantees correct order of reads and writes.
Signed-off-by: Juhamatti Kuusisaari
---
12 matches
Mail list logo
