On Mon, May 14, 2018 at 08:57:55AM +0200, Peter Zijlstra wrote:
> On Fri, May 11, 2018 at 09:20:53AM -0700, Paul E. McKenney wrote:
> > On Fri, May 11, 2018 at 10:32:42AM +0200, Peter Zijlstra wrote:
> > > On Fri, May 11, 2018 at 03:25:18PM +0800, Xiao Guangrong wrote:
> > > >
> > > > Hi,
> > > >
On Fri, May 11, 2018 at 09:20:53AM -0700, Paul E. McKenney wrote:
> On Fri, May 11, 2018 at 10:32:42AM +0200, Peter Zijlstra wrote:
> > On Fri, May 11, 2018 at 03:25:18PM +0800, Xiao Guangrong wrote:
> > >
> > > Hi,
> > >
> > > Currently, there is no read barrier between reading the index
> > > (
On Fri, May 11, 2018 at 10:32:42AM +0200, Peter Zijlstra wrote:
> On Fri, May 11, 2018 at 03:25:18PM +0800, Xiao Guangrong wrote:
> >
> > Hi,
> >
> > Currently, there is no read barrier between reading the index
> > (kfifo.in) and fetching the real data from the fifo.
> >
> > I am afraid that wi
On Fri, May 11, 2018 at 03:25:18PM +0800, Xiao Guangrong wrote:
>
> Hi,
>
> Currently, there is no read barrier between reading the index
> (kfifo.in) and fetching the real data from the fifo.
>
> I am afraid that will cause the vfifo is observed as not empty
> however the data is not actually r
My guts thinks you are right. Feel free to send a patch...
Am Freitag, den 11.05.2018, 15:25 +0800 schrieb Xiao Guangrong:
> Hi,
>
> Currently, there is no read barrier between reading the index
> (kfifo.in) and fetching the real data from the fifo.
>
> I am afraid that will cause the vfifo is o
Hi,
Currently, there is no read barrier between reading the index
(kfifo.in) and fetching the real data from the fifo.
I am afraid that will cause the vfifo is observed as not empty
however the data is not actually ready for read. Right?
Thanks!
6 matches
Mail list logo