On Thu, 5 Apr 2018, Peter Zijlstra wrote:
> On Thu, Apr 05, 2018 at 10:35:22AM -0400, Alan Stern wrote:
> > In this example, READ_ONCE() is in fact a volatile access, so we're
> > okay.
>
> But our documentation clearly states a control-dep can only be from a
> READ_ONCE() (or something
On Thu, 5 Apr 2018, Peter Zijlstra wrote:
> On Thu, Apr 05, 2018 at 10:35:22AM -0400, Alan Stern wrote:
> > In this example, READ_ONCE() is in fact a volatile access, so we're
> > okay.
>
> But our documentation clearly states a control-dep can only be from a
> READ_ONCE() (or something
On Thu, Apr 05, 2018 at 10:35:22AM -0400, Alan Stern wrote:
> In this example, READ_ONCE() is in fact a volatile access, so we're
> okay.
But our documentation clearly states a control-dep can only be from a
READ_ONCE() (or something stronger), right? So we should be good
irrespectively.
On Thu, Apr 05, 2018 at 10:35:22AM -0400, Alan Stern wrote:
> In this example, READ_ONCE() is in fact a volatile access, so we're
> okay.
But our documentation clearly states a control-dep can only be from a
READ_ONCE() (or something stronger), right? So we should be good
irrespectively.
On Thu, 5 Apr 2018, Peter Zijlstra wrote:
> On Wed, Apr 04, 2018 at 04:35:32PM -0400, Alan Stern wrote:
> > On Wed, 4 Apr 2018, Daniel Jordan wrote:
> >
> > > A question for memory-barriers.txt aficionados.
> > >
> > > Is there a control dependency between the prior load of 'a' and the
> > >
On Thu, 5 Apr 2018, Peter Zijlstra wrote:
> On Wed, Apr 04, 2018 at 04:35:32PM -0400, Alan Stern wrote:
> > On Wed, 4 Apr 2018, Daniel Jordan wrote:
> >
> > > A question for memory-barriers.txt aficionados.
> > >
> > > Is there a control dependency between the prior load of 'a' and the
> > >
On Wed, Apr 04, 2018 at 04:35:32PM -0400, Alan Stern wrote:
> On Wed, 4 Apr 2018, Daniel Jordan wrote:
>
> > A question for memory-barriers.txt aficionados.
> >
> > Is there a control dependency between the prior load of 'a' and the
> > later store of 'c'?:
> >
> >while (READ_ONCE(a));
> >
On Wed, Apr 04, 2018 at 04:35:32PM -0400, Alan Stern wrote:
> On Wed, 4 Apr 2018, Daniel Jordan wrote:
>
> > A question for memory-barriers.txt aficionados.
> >
> > Is there a control dependency between the prior load of 'a' and the
> > later store of 'c'?:
> >
> >while (READ_ONCE(a));
> >
On 04/04/2018 04:35 PM, Alan Stern wrote:
On Wed, 4 Apr 2018, Daniel Jordan wrote:
A question for memory-barriers.txt aficionados.
Is there a control dependency between the prior load of 'a' and the
later store of 'c'?:
while (READ_ONCE(a));
WRITE_ONCE(c, 1);
I would say that yes,
On 04/04/2018 04:35 PM, Alan Stern wrote:
On Wed, 4 Apr 2018, Daniel Jordan wrote:
A question for memory-barriers.txt aficionados.
Is there a control dependency between the prior load of 'a' and the
later store of 'c'?:
while (READ_ONCE(a));
WRITE_ONCE(c, 1);
I would say that yes,
On Wed, 4 Apr 2018, Daniel Jordan wrote:
> A question for memory-barriers.txt aficionados.
>
> Is there a control dependency between the prior load of 'a' and the
> later store of 'c'?:
>
>while (READ_ONCE(a));
>WRITE_ONCE(c, 1);
I would say that yes, there is.
> I have my doubts
On Wed, 4 Apr 2018, Daniel Jordan wrote:
> A question for memory-barriers.txt aficionados.
>
> Is there a control dependency between the prior load of 'a' and the
> later store of 'c'?:
>
>while (READ_ONCE(a));
>WRITE_ONCE(c, 1);
I would say that yes, there is.
> I have my doubts
A question for memory-barriers.txt aficionados.
Is there a control dependency between the prior load of 'a' and the
later store of 'c'?:
while (READ_ONCE(a));
WRITE_ONCE(c, 1);
I have my doubts because memory-barriers.txt doesn't talk much about
loops and because of what that document
A question for memory-barriers.txt aficionados.
Is there a control dependency between the prior load of 'a' and the
later store of 'c'?:
while (READ_ONCE(a));
WRITE_ONCE(c, 1);
I have my doubts because memory-barriers.txt doesn't talk much about
loops and because of what that document
14 matches
Mail list logo