public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Pranith Kumar <pranith@gatech.edu>
Cc: Peter Zijlstra <peterz@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Question regarding "Control Dependencies" in memory-barriers.txt
Date: Mon, 4 Aug 2014 11:52:26 -0700	[thread overview]
Message-ID: <20140804185226.GQ8101@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAJhHMCADiEsUC7GsYF7=qMNEyRJerfhC5zh7WQPgkQ0gJn5=5A@mail.gmail.com>

On Mon, Aug 04, 2014 at 01:07:47PM -0400, Pranith Kumar wrote:
> The section "Control Dependencies" in memory-barriers.txt has the
> following text:
> 
> 662 In addition, you need to be careful what you do with the local variable 'q',
> 663 otherwise the compiler might be able to guess the value and again remove
> 664 the needed conditional.  For example:
> 665
> 666         q = ACCESS_ONCE(a);
> 667         if (q % MAX) {
> 668                 barrier();
> 669                 ACCESS_ONCE(b) = p;
> 670                 do_something();
> 671         } else {
> 672                 barrier();
> 673                 ACCESS_ONCE(b) = p;
> 674                 do_something_else();
> 675         }
> 676
> 677 If MAX is defined to be 1, then the compiler knows that (q % MAX) is
> 678 equal to zero, in which case the compiler is within its rights to
> 679 transform the above code into the following:
> 680
> 681         q = ACCESS_ONCE(a);
> 682         ACCESS_ONCE(b) = p;
> 683         do_something_else();
> 
> Given that there is an explicit barrier() in both the branches of
> if/else statement, how can the above transformation happen? The
> compiler cannot just remove the barrier(), right?

No, the compiler cannot just remove the barrier().  However, it can
notice that "q % MAX" is always zero, which allows it to throw away
the then-clause entirely.

> I think it will transform to the following if MAX is defined to 1:
> 
> q = ACCESS_ONCE(a);
> barrier();
> ACCESS_ONCE(b) = p;
> do_something_else();

Good point, the "barrier()" must be retained, but...

> and hence the ordering will be preserved. What am I missing here?

Because the barrier() primitive affects only the compiler, the CPU
can still reorder things.

In contrast, in the original, the control dependency implied by the "if"
statement prevents the CPU from reordering.

I fixed the example to retain the barrier() with your Reported-by.

						Thanx, Paul


  reply	other threads:[~2014-08-04 18:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04 17:07 Question regarding "Control Dependencies" in memory-barriers.txt Pranith Kumar
2014-08-04 18:52 ` Paul E. McKenney [this message]
2014-08-04 21:03   ` Pranith Kumar
2014-08-05  7:32     ` Peter Zijlstra
2014-08-05 12:13       ` Pranith Kumar
2014-08-05 12:58         ` Peter Zijlstra
2014-08-13 22:44         ` Paul E. McKenney
2014-08-14  0:10           ` Pranith Kumar
2014-08-14  0:35             ` Paul E. McKenney
2014-08-14  1:03               ` Pranith Kumar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140804185226.GQ8101@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=pranith@gatech.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox